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

Uploads of large objects to Oracle Storage Cloud Service fail with 400 error reply #9223

Closed
cyberduck opened this issue Jan 19, 2016 · 11 comments
Closed
Assignees
Labels
bug fixed high priority openstack version:4.7.3
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 19, 2016

5d2bd01 created the issue

We were trying to certify Cyberduck with Oracle Storage Cloud Services and found out that for smaller object uploads works fine, but larger objects, typically > 3GB uploads always fails with an error to retry/continue. From our systems only about 1 GB file uploads worked successfully. Our work flow demands upwards of 50 to 60 GB single file/object upload to be successful, which unfortunately we have not had luck with.

A large object download also gave up problems (about 10 GB).

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 21, 2016

@dkocher commented

Possibly related to #9131. Although this ticket only affect files greater than 100GB.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 21, 2016

@dkocher commented

Please post the transcript from the log drawer of the Transfers window. Choose ⌘-L on Mac or right-click the toolbar from the Transfers window and choose Log on Windows

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 21, 2016

@dkocher commented

Please update to the latest snapshot build available when testing again.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 23, 2016

5d2bd01 commented

There was nothing logged to the console/window when I try the upload of a 3.2 GB file. I get a screen that pops up that says the command failed and gives me an option to continue. And if I do, it retries the upload and fails.

The upload never succeeds.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 29, 2016

@dkocher commented

Surely the transfer log drawer contains the HTTP transcript. Please attach.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 29, 2016

@dkocher commented

Would it be possibly to activate our identity domain again [1] which would allow us to assist you in testing.

[1] Identity Domain: chiterategmbhtrial85243

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 11, 2016

@dkocher commented

Handled in case CD-52.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 24, 2016

@dkocher commented

Fixed stream progress reset in b69f593 for failed segments.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 24, 2016

@dkocher commented

The issue is caused by URI encoded forward slashes in the object name.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 24, 2016

@dkocher commented

Added test in 12f397b.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 24, 2016

@dkocher commented

Fix in f5e4c02 from upstream changeset.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed high priority openstack version:4.7.3
Projects
None yet
Development

No branches or pull requests

2 participants