bootstrap aws fails but leaves instance alive

Bug #1560888 reported by Matthew Williams on 2016-03-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

After bootstrap I got the following messages:

It's not clear from this output if bootstrap worked or not. But when I do juju status:

$ juju status
ERROR Unable to connect to model "".
Please check your credentials or use 'juju bootstrap' to create a new model.

Error details:
no model specified

That suggests that it didn't work.

When I log into my aws console I can see that there is a machine active

Cheryl Jennings (cherylj) wrote :

It would seem we should also retry the API connection on a "maintenance in progress" error... and also clean up on a failure.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-beta4
tags: added: bootstrap juju-release-support
tags: added: 2.0-count
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.1
affects: juju-core → juju
Changed in juju:
milestone: 2.0.1 → none
milestone: none → 2.0.1
Curtis Hovey (sinzui) on 2016-10-28
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers