Comment 1 for bug 1997235

I don't disagree with the sentiment in the bug report. The active, blocked, error, unknown statuses are currently viewed (by the charm) from the perspective of "whether that instance is working correctly". The 'cluster-level' view status doesn't really exist, as it's a meta-state of the complete cluster.

We'd need to change the meaning of the unit status *when clustered* to mean something subtly-else which is a compound of the individual unit status and the overall cluster health, which is what the status message is trying to indicate - i.e. the charm is aware of the cluster status.

Ideally, there would be a 'degraded' status (or similar) that could be set to indicate a cluster-level status, AND the ability of the units to to indicate their individual statuses. Sadly, this isn't currently available.

I'd probably be okay with changing the status to blocked in the event that the cluster is degraded, but interested in other viewpoints.