Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to change storage class of file in vault #11830

Closed
cyberduck opened this issue Sep 28, 2021 · 10 comments
Closed

Unable to change storage class of file in vault #11830

cyberduck opened this issue Sep 28, 2021 · 10 comments
Assignees
Labels
bug s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

186d225 created the issue

Hallo, ich habe Daten in einem Cryptomator Vault in einem Scaleway Bucket
hochgeladen.
Dieses anschließend in die Speicherklasse Glacier verschoben.

Wenn ich nun eine Datei daraus herunterladen möchte und über die
Dateiinformationen die Klasse auf Standard ändern möchte erhalte ich von
Cyberduck den Fehler:

Your proposed upload exceeds the maximum allowed object size. Please
contact your web host for further assistance.

Die Datei ist jedoch nur knapp 4 MB groß.
Der Scaleway Support verweist auf Cyberduck.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Relates to #11751.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I am unable to reproduce the problem with AWS.

@cyberduck
Copy link
Collaborator Author

186d225 commented

Replying to [comment:3 dkocher]:

I am unable to reproduce the problem with AWS.

I have the problem with Scaleway Object Storage.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 1ae9a64. Scaleway only supports STANDARD and GLACIER options.

Screenshot 2021-10-15 at 11.22.25.png

@cyberduck
Copy link
Collaborator Author

186d225 commented

I have done a few tests.
My bucket is in Amsterdam, in it are vaults as well as unencrypted data.

Unencrypted:
I can create new folders and files via Cyberduck. These are displayed correctly and I can download them.
As soon as I change them via the file Info to class "Glacier" the class is changed to Glacier, but afterwards I cannot change the file via the file Information to "Standard".

The only way to get the file back to the default class is through the Scaleway website.

Encrypted:
Same behavior as above.
The workaround to change files to standard class via the web page is immensely more difficult in Vaults, because the files are not recognizable and you can't change a complete folder to standard via the Scaleway web page.

So there seems to be a problem / change on the part of the API (?) that prevents the change of any files (encrypted / unencrypted) from Glacier -> Standard.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:7 blueman]:

I have done a few tests.
My bucket is in Amsterdam, in it are vaults as well as unencrypted data.

Unencrypted:
I can create new folders and files via Cyberduck. These are displayed correctly and I can download them.
As soon as I change them via the file Info to class "Glacier" the class is changed to Glacier, but afterwards I cannot change the file via the file Information to "Standard".

The only way to get the file back to the default class is through the Scaleway website.

Encrypted:
Same behavior as above.
The workaround to change files to standard class via the web page is immensely more difficult in Vaults, because the files are not recognizable and you can't change a complete folder to standard via the Scaleway web page.

So there seems to be a problem / change on the part of the API (?) that prevents the change of any files (encrypted / unencrypted) from Glacier -> Standard.

Is this possibly related to #11751?

@cyberduck
Copy link
Collaborator Author

186d225 commented

Replying to [comment:8 dkocher]:

Is this possibly related to #11751?

I'm sorry, I can't answer that.

I just tested the whole thing on a completely different Mac with Cyberduck V. 7.10.1.
There it behaves exactly the same.

Standard -> Glacier: works
Glacier -> Standard: error

Workaround:
Manually change file to default class via Scaleway web page.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:9 blueman]:

Replying to [comment:8 dkocher]:

Is this possibly related to #11751?

I'm sorry, I can't answer that.

I just tested the whole thing on a completely different Mac with Cyberduck V. 7.10.1.
There it behaves exactly the same.

Standard -> Glacier: works
Glacier -> Standard: error

Workaround:
Manually change file to default class via Scaleway web page.

Duplicate for #11849.

@cyberduck
Copy link
Collaborator Author

186d225 commented

I just tested the issue again with Cyberduck 8.0.0. Unfortunately, the error is still there.
I still cannot change files from Glacier to the Standard class.

The error:

Your proposed upload exceeds the maximum allowed object size. Please contact your web host for further assistance.

It is irrelevant whether it is in a Vault or an unencrypted file.

@blu-e-man
Copy link

Hello, I was the creator of this error in the other platform.
I would like to give an update.

With Scaleway Support and their Advanced Team it took me two months (!) to manually transfer data from Glacier to Standard class.
Neither via the CLI nor via the GUI the data could be transferred to Standard.

Unfortunately, support did not communicate where the problem was or is. Therefore, I assume that the error is on the part of Scaleway, since their systems do not work cleanly and do not execute the commands again CLI.

@dkocher dkocher closed this as completed Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

3 participants