Status is not consistent with actual status - status is stuck on install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
After a load test has been running for a while, I come back to look at juju status as and see a unit in maintenance (installing agent):
$ juju status scrape-config/0
Model Controller Cloud/Region Version SLA Timestamp
cos-lite-load-test uk8s microk8s/localhost 2.9.32 unsupported 14:08:36Z
App Version Status Scale Charm Channel Rev Address Exposed Message
scrape-config waiting 1 prometheus-
Unit Workload Agent Address Ports Message
scrape-config/0* maintenance idle 10.1.79.207
On the other hand, show-status-log suggests that we're past install and already after start:
$ juju show-status-log scrape-config/0
Time Type Status Message
28 Jun 2022 11:05:33Z workload active
28 Jun 2022 13:04:02Z workload maintenance stopping charm software
28 Jun 2022 13:04:02Z juju-unit executing running stop hook
28 Jun 2022 13:04:06Z juju-unit executing running start hook
28 Jun 2022 13:05:44Z juju-unit idle
28 Jun 2022 13:05:44Z workload maintenance
The log seems to confirm
$ juju debug-log --include unit-scrape-
unit-scrape-
unit-scrape-
unit-scrape-
unit-scrape-
unit-scrape-
unit-scrape-
unit-scrape-
unit-scrape-
unit-scrape-
unit-scrape-
So it seems that `juju status` is not consistent with the actual status.
This looks like an issue with the model cache not being updated.
Are there any controller log errors?