ERROR: model has been removed
Bug #1721786 reported by
Cory Johns
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Anastasia |
Bug Description
On the edge snap of Juju, with the LXD provider, when adding and removing models in parallel, the controller seems to get into a bad state where you cannot list models or even destroy the controller because of an error stating that a particular model "has been removed"
Changed in juju: | |
milestone: | none → 2.3-beta2 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
importance: | High → Critical |
Changed in juju: | |
status: | Incomplete → Triaged |
Changed in juju: | |
assignee: | nobody → Anastasia (anastasia-macmood) |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I started seeing this when running the integration tests in python-libjuju (tox -e integration), which runs a bunch of tests in parallel, most of which create their own unique model to run in which they remove when complete. One of the tests tests ControllerFacad e.AllModels which sometimes returns this error. But we've also seen all tests pass (including that one) and it show up during tear down of the lxd controller. I also hit an instance where I ran the tests on a local lxd controller and the error persisted after the tests and through multiple interactions via the CLI, as shown in the pastebin, so it doesn't seem strictly like a timing issue.