Juju fails to report it cannot create buckets
Bug #1494798 reported by
Curtis Hovey
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
CI reported a systemic failure testing in AWS:
ERROR .* failed to bootstrap environment: cannot start bootstrap instance: recording instance in provider-state: cannot write file "provider-state" to control bucket: The specified bucket does not exist
We discovered that our account had reached its limit of containers, but juju failed to tell us this. Juju needs to tell users that they have exceeded their resource limits to allow juju to work.
http://
Another solution is to stop using s3.
| description: | updated |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This issue has not been seen in 9 months.