Destroying models can use juju to consider the controller to already be removed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Anastasia |
Bug Description
As seen here: http://
Similar to the bug lp:1721786, it's possible that when destroying models and then attempting to destroy the controller this can fail as juju considers the controller to already be removed:
"Unable to destroy controller through the API: model 4bdbb8af-
This can be seen in this run here: http://
It appears to be intermittent.
Initial repro steps:
- Bootstrap
- Create 3 or so models
- Deploy something to these models (unsure yet if step is required)
- Ensure deployed charms are working
- Destroy each model in turn
- Attempt to destroy the controller
tags: | added: ci |
Changed in juju: | |
status: | Fix Committed → Fix Released |
PR against develop: https:/ /github. com/juju/ juju/pull/ 8006
Although, it is really not simple to repro due to its intermittent nature :(
Hopefully, with CI now closely monitoring it, we'd be in a better position to observe/determine what info we need to eliminate it once and for all...