Failed instance start doesn't surface error.

Bug #2046524 reported by Thomas Miller
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Thomas Miller

Bug Description

I noticed that when bootstrapping to Oracle cloud we had an account problem that was stopping us from bootstrapping in any of the availability zones. After some digging we are not transmitting the start instance errors back to the caller so we end up with error messages like this.

ERROR failed to bootstrap model: cannot start bootstrap instance in any availability zone (qIZq:PHX-AD-1, qIZq:PHX-AD-2, qIZq:PHX-AD-3):

Not very helpful for the user unless they know to go looking at debug logs.

Thomas Miller (tlmiller)
Changed in juju:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Thomas Miller (tlmiller)
milestone: none → 4.0-beta2
Changed in juju:
milestone: 4.0-beta2 → 4.0-beta3
Changed in juju:
status: In Progress → Triaged
Changed in juju:
milestone: 4.0-beta3 → 4.0-beta4
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.