show-status and list-models disagree after migration
Bug #1613311 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
After migration, it appears that show-status lags list-models in determining that the model is present in the new controller. This is intermittent (probably timing-dependant).
As seen here:
http://
What's not shown in the output, but I have verified by looking at the test code, is that we run list-models repeatedly until the migrated model is listed. Only then do we run show-status. So when show-status reports "model ... not found", it is disagreeing with list-models.
| description: | updated |
| summary: |
- show-log and list-models disagree after migration + show-status and list-models disagree after migration |
| affects: | juju-core → juju |
| Changed in juju: | |
| assignee: | nobody → Menno Smits (menno.smits) |
| Changed in juju: | |
| milestone: | none → 2.1.0 |
| Changed in juju: | |
| status: | Triaged → Fix Committed |
| status: | Fix Committed → Triaged |
| Changed in juju: | |
| assignee: | Menno Smits (menno.smits) → nobody |
| status: | Triaged → Fix Released |
To post a comment you must log in.
