-
Notifications
You must be signed in to change notification settings - Fork 37
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
multipart upload fails sporadically #834
Comments
I'm actually still seeing this when trying to push resources to the charmstore.
Also, #849 seems to be a dupe of this, showing others having this problem. |
The 411 on resume started after the upload failed the first time:
|
Reattempting after clearing the charm upload cache resulted in
Resuming upload reliably triggered 411. Additionally the 411 occurred when re-attempting after cancelling charm-attach with ctrl+c. After several attempts via clearing the cache and retrying, I was able to upload, so there is a (painful) workaround. |
To be clear here the 411 error here comes from the charmstore to swift link. It is possible that #854 will alleviate this. |
The most salient error message seems to be this one:
which indicates that there's some kind of transient error trying to upload to Swift. We should add a retry loop inside the charmstore blobstore code for this kind of situation. |
When uploading a multipart resource, we occasionally see a 411 response followed by the upload failing.
Here's a client-side log of the problem:
resource-multipart-upload-error-2018-09-20.txt
A representative error log line from the squid proxy is:
The body of the response was:
squid-error-2018-09-20.txt
The text was updated successfully, but these errors were encountered: