misleading application status if charm does not set a status
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
If a charm doesn't set any status, the `juju status` output is somewhat misleading. It appears to be hanging at waiting for "installing agent". While actually here it's all up and running, just the charm hasn't set a status yet. For example:
```
Model Controller Cloud/Region Version SLA Timestamp
zaza-8bc91a62ca54 server-microk8s server-
App Version Status Scale Charm Channel Rev Address Exposed Message
glance waiting 1 glance-k8s edge 3 10.152.183.227 no installing agent
keystone waiting 1 keystone-k8s 0 10.152.183.110 no installing agent
mysql active 1 sunbeam-mysql-k8s beta 4 10.152.183.101 no
Unit Workload Agent Address Ports Message
glance/0* unknown idle 10.1.206.224
keystone/0* unknown idle 10.1.206.194
mysql/0* active idle 10.1.206.216
```
It would be nice if juju cleared the application status, or updated it to some message to indicate that everything was successful with the agent and now it's handed status control over to the charm.
Changed in juju: | |
milestone: | 2.9.34 → 2.9.35 |
Changed in juju: | |
milestone: | 2.9.35 → 2.9.36 |
Changed in juju: | |
milestone: | 2.9.36 → 2.9.37 |
Changed in juju: | |
milestone: | 2.9.37 → 2.9.38 |
Changed in juju: | |
milestone: | 2.9.38 → 2.9.39 |
Changed in juju: | |
milestone: | 2.9.39 → 2.9.40 |
Changed in juju: | |
milestone: | 2.9.40 → 2.9.41 |
Changed in juju: | |
milestone: | 2.9.41 → 2.9.42 |
Changed in juju: | |
milestone: | 2.9.42 → 2.9.43 |
Changed in juju: | |
milestone: | 2.9.43 → 2.9.44 |
Changed in juju: | |
milestone: | 2.9.44 → 2.9.45 |
Changed in juju: | |
milestone: | 2.9.45 → 2.9.46 |
The message displayed in the `juju status` is a section reserved for charms. This means that if Juju sets the value of this field, it may disrupt the charm lifecycle with erroneous messages. This is more a charm design issue rather than a Juju problem. Said that, we will consider this comment for further improvement. Thanks for taking your time to report this.