Code review comment for lp:~mskalka/juju-ci-tools/assess-destroy-model
Revision history for this message
| Aaron Bentley (abentley) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
> Hmm. I don't see a report linked for the timing hole
The report of the timing hole is bug #1582021 itself.
It is the fact that "list-models" errors with "model not found". It is not erroring because the current-model is wrong. It is erroring because "we first get all models, then query each one for more details"
"bigdata" was in the first list, but was not accessible when queried, producing the "model not found" error.
A correct test for this would be something like:
juju bootstrap --default-model foobar
juju destroy-model foobar
# Avoid bug 1505504.
juju switch controller
# If we have a timing hole, this fails with "model not found"
juju list-models
This test should be run against 2.0-beta7 (or earlier) to prove that it fails, with 2.0-beta8 to prove that it fails even with bug #1505504 fixed, and then with current juju to prove that it passes.