[gce] odd error messages are printed with kill-controller
Bug #1831527 reported by
Peter Matulis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Low
|
Anastasia | ||
2.5 |
Fix Released
|
Low
|
Anastasia | ||
2.6 |
Fix Released
|
Low
|
Anastasia |
Bug Description
juju bootstrap --credential gandalf google gce
juju deploy cs:canonical-
juju status
Output:
https:/
juju kill-controller --debug -y -t0 gce
Output:
https:/
The cloud vendor's dashboard shows all instances have been removed.
Although output is drawn out, destroy-controller works without these errors:
juju destroy-controller -y --destroy-
Output:
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I am not sure why you have observed the errors. I am in the process of trying to reproduce what you were seeing...
I've noticed that the instances that were 'not found' but destroyed anyway were on either us-east1-b or us-east1-c. Maybe these zones were more efficient at a time? :)
Anyway, at a cursory glance it looks like some kind of timing issue and the fact that everything gets destroyed successfully in the end is good news. I'll triage this a Low priority.