Juju fails to report it cannot create buckets

Bug #1494798 reported by Curtis Hovey
16
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://reports.vapour.ws/releases/issue/55d4fac1749a561807a8117b

Another solution is to stop using s3.

Curtis Hovey (sinzui)
description: updated
Revision history for this message
Curtis Hovey (sinzui) wrote :

This issue has not been seen in 9 months.

Changed in juju-core:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.