"juju models" reporting bad number of machines
Bug #1780189 reported by
Junien F
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Hi,
I have a model hosted on a JAAS controller. When I run "juju models", my model is displayed as having 9 machines and 13 cores, but in reality (and in the controller database), there are only 2 machines (machine 0 and machine 8, so presumably we did create 9 at some point).
Not sure if this is a JAAS bug or juju bug ("juju models --debug" only shows connections to jimm.jujucharms.com and not to the controller itself).
This is with juju 2.3.8.
Thanks
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| tags: | added: usability |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
It is possible that for speed of response, we are looking at client side cache and not actually querying the controller. We had similar issues with models command on 'controllers' command.
I'll investigate further and will keep you posted.