Canonical Juju

list-models fails after model is destroyed after model migration

Bug #1674805 reported by Curtis Hovey
38
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Anastasia
Canonical Juju 2.2-beta3

Bug Description

as seen at
    http://reports.vapour.ws/releases/issue/57d08664749a561ebb925b1a

list-models failed immediately after a model was destroyed. Though bug 1667333 is fixed released, we can see from the history of the issue that the commit did not affect the rate of failure

All hosted models reclaimed, cleaning up controller machines
02:23:59 INFO juju.provider.common destroy.go:20 destroying model "controller"
02:23:59 INFO juju.provider.common destroy.go:31 destroying instances
02:24:09 INFO juju.provider.common destroy.go:51 destroying storage
02:24:09 INFO cmd supercommand.go:465 command finished
2017-02-23 02:24:09 ERROR Command '('juju', '--show-log', 'list-models', '-c', 'functional-model-migration-joyent-b')' returned non-zero exit status 1

Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.2-beta1 → 2.2-beta2
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Related to bug # 1676279.

Anastasia (anastasia-macmood)
Changed in juju:
milestone: 2.2-beta2 → 2.2-beta3
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I am convinced that this is not about listing the models now but is, in fact, related to a different issue where we could not destroy a model. The fix for for destroying models cleanly went into develop. I would prefer to wait and see if this failure will go away once we cleanly destroy models.

Drive-by fix was in PR https://github.com/juju/juju/pull/7184/

Changed in juju:
status: Triaged → Incomplete
milestone: 2.2-beta3 → none
Anastasia (anastasia-macmood)
Changed in juju:
milestone: none → 2.2-beta3
assignee: nobody → Anastasia (anastasia-macmood)
status: Incomplete → Triaged
Revision history for this message
Anastasia (anastasia-macmood) wrote :

PR agaisnt develop (2.2): https://github.com/juju/juju/pull/7265

Changed in juju:
status: Triaged → In Progress
Anastasia (anastasia-macmood)
Changed in juju:
status: In Progress → Fix Committed
Canonical Juju QA Bot (juju-qa-bot)
Changed in juju:
status: Fix Committed → Fix Released
Revision history for this message
gdupont (ger-dupont) wrote :

Hi guys,
I think I get a similar issue here on 2.2.3-xenial-amd64. I lost connection to the controller during model destruction and since then, I cannot list models:

$juju list-models
ERROR cannot get model details: getting model 4798e673-3baf-42f5-892b-d30957a4f55a ("stack-mk25") info: settings not found

Not it's the same root cause but symptoms are similar. If logs are needed, I can dig (but I would need some guidance).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.