juju show-status fails during teardown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Anastasia |
Bug Description
It is unclear if this is a bug in the test assumptions, or a bug in 'juju show-status', but we're having CI runs fail because of it:
http://
http://
My first thought is that it is a problem with the test suite. Certainly if you do "juju show-status DYINGMODEL" and that model actually dies, we would expect status to fail, wouldn't we?
Maybe the model should still be there?
2018-01-11 12:33:00 INFO juju --show-log show-status -m destroy-
...
ERROR model "test-tmp-env" has been removed from the controller, run 'juju models' and switch to one of them.
...
raceback (most recent call last):
File "/var/lib/
sys.
File "/var/lib/
assess_
File "/usr/lib/
self.gen.next()
File "/var/lib/
yield machines
File "/usr/lib/
self.gen.next()
File "/var/lib/
m_client.
File "/var/lib/
self.
File "/var/lib/
model, check, timeout, extra_env, suppress_
File "/var/lib/
rval = call_func(args, stderr=stderr)
File "/usr/lib/
raise CalledProcessEr
subprocess.
That sure looks like were getting a non-zero return code, but because the model really isn't there.
Maybe its more the issue that "juju models" is listing models that are in a dying/dead state? There seem to be other bugs around that.
Changed in juju: | |
status: | Fix Committed → Fix Released |
I believe this was fixed by other fixes from Anastasia.