Client loses information about current model
Bug #1796148 reported by
Jacek Nykis
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Anastasia | ||
2.4 |
Fix Released
|
High
|
Anastasia |
Bug Description
We have a large, shared juju controller with multiple models.
Recently clients started loosing information about current model. When this happens "juju status" returns:
ERROR current model for controller XXX not found
I can see model information in ~/.local/
"juju list-models" shows the model and when I run "juju switch $model" it works just fine:
XXX (controller) -> XXX:admin/YYY
After this operation current-model appears in models.yaml and juju status works fine.
juju client version 2.4.3-trusty-amd64
Both controller and my "user" model are on 2.4.3
summary: |
- Client looses information about current model + Client loses information about current model |
Changed in juju: | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5-beta1 |
Changed in juju: | |
status: | Incomplete → Confirmed |
Changed in juju: | |
status: | Confirmed → Triaged |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Is there any sort of hint what precedes the loss of the current model info? I can understand that if the current model is empty you get the message about status giving an error, but I wonder how that got lost. Is there multiple folks on there running simultaneous commands as the same user or something that might be confusing the code around recording the current model?