incorrect k8s sidecar charm app status

Bug #1934614 reported by Ian Booth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Yang Kelvin Liu

Bug Description

deploy a sidecar charm and run status
The application status shows as "Active" when clearly things are not ready.
The application status should reflect anything explicitly set by the charm, or an aggregation of the individual unit status values. In the case below, it should be "waiting".

NB operator charms (v1) do have the correct behaviour.

$ juju status
Model Controller Cloud/Region Version SLA Timestamp
controller ian microk8s/localhost 2.9.8 unsupported 12:23:37+10:00

App Version Status Scale Charm Store Channel Rev OS Address Message
mysql-k8s active 0/1 mysql-k8s charmhub stable 2 kubernetes 10.152.183.104

Unit Workload Agent Address Ports Message
mysql-k8s/0 waiting allocating 10.1.78.120 installing agent

Changed in juju:
milestone: 2.9.8 → 2.9.9
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
Changed in juju:
milestone: 2.9.9 → 2.9.10
Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.