juju wait-for unit checks application message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
When I shutdown one unit of an application and then try to check wait-for message it shows wrong information
$ juju status aodh/1
Model Controller Cloud/Region Version SLA Timestamp
openstack foundations-maas maas_cloud/default 2.9.37 unsupported 16:03:11Z
App Version Status Scale Charm Channel Rev Exposed Message
aodh 14.0.0 active 0/1 aodh yoga/stable 77 no Unit is ready
aodh-mysql-router 8.0.31 active 0/1 mysql-router 8.0/stable 35 no Unit is ready
hacluster-aodh active 0/1 hacluster 2.4/stable 117 no Unit is ready and clustered
logrotated active 0/1 logrotated stable 7 no Unit is ready.
public-
Unit Workload Agent Machine Public address Ports Message
aodh/1 unknown lost 1/lxd/0 10.246.166.156 8042/tcp agent lost, see 'juju show-status-log aodh/1'
aodh-
hacluster-aodh/0 unknown lost 10.246.166.156 agent lost, see 'juju show-status-log hacluster-aodh/0'
logrotated/37 unknown lost 10.246.166.156 agent lost, see 'juju show-status-log logrotated/37'
public-
$ juju wait-for unit aodh/1
Unit "aodh/1" is running
properties:
life: alive
workload-status: active
It looks like it is getting status and message from the application, not from the unit
$ juju wait-for unit aodh/1 --query 'workload-
Unit "aodh/1" is running
properties:
workload-message: Unit is ready
workload-status: active
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: wait-for |