-
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
Can't push to staging charmstore #818
Comments
We don't think this is a charmstore issue. See go-goose/goose#66 |
@wallyworld I don't know if that issue is the cause of the failures I see because it would imply that immediately calling |
It's also worth noting that even for a brand new charm or bundle, when it fails the rev counter gets incremented even when nothing gets uploaded. An example:
Then:
|
@wallyworld, it looks like the charmstore imports swift from github.com/ncw/swift, not the goose version? I tracked the error to the blob store, but I haven't found the link from the blob store to goose/swift yet. |
I'm unable to push a charm to staging for testing:
The text was updated successfully, but these errors were encountered: