workload unknown

[yanxiaomu]

juju status rsyslog-forwarder-ha
Model Controller Cloud/Region Version SLA Timestamp
openstack maas-controller mymaas/default 2.8.10 unsupported 15:43:40+08:00

App Version Status Scale Charm Store Rev OS Notes
ceph-osd 15.2.8 active 3 ceph-osd jujucharms 308 ubuntu
masakari-monitors 10.0.0 active 0 masakari-monitors local 0 ubuntu
nova-compute active 0 nova-compute jujucharms 325 ubuntu
ntp 3.5 active 0 ntp local 0 ubuntu
ovn-chassis 20.03.1 active 0 ovn-chassis local 0 ubuntu
pacemaker-remote active 0 pacemaker-remote local 0 ubuntu
rsyslog-forwarder-ha unknown 3 rsyslog-forwarder-ha jujucharms 20 ubuntu

Unit Workload Agent Machine Public address Ports Message
ceph-osd/0 active idle 0 10.0.0.156 Unit is ready (1 OSD)
  rsyslog-forwarder-ha/7 unknown idle 10.0.0.156
ceph-osd/1 active idle 1 10.0.0.159 Unit is ready (1 OSD)
  rsyslog-forwarder-ha/6* unknown idle 10.0.0.159
ceph-osd/2* active idle 2 10.0.0.158 Unit is ready (1 OSD)
  rsyslog-forwarder-ha/8 unknown idle 10.0.0.158

Machine State DNS Inst id Series AZ Message
0 started 10.0.0.156 node2 focal default Deployed
1 started 10.0.0.159 node4 focal default Deployed
2 started 10.0.0.158 node3 focal default Deployed

[Edward Hope-Morley (hopem)]

I have reproduced this with the latest version of the charm and it is simply a result of the fact that the charm only calls status_set in the config-changed hook which will only run if config is actually changed. So for example if you subsequently do juju config rsyslog-forwarder-ha watch-files=/my/file that will trigger config-changed and the workload will go to "active".