We've seen this happen too. It seems the charm sets a default value for is_started[1] to False and never updates that local state to True once the charm is fully configured and active[2].
The fix would be to set that stored value to False in the charm if the status is not active[3] and set it to true if it passes that check[4].
The message is harmless, but it does introduce a measure of doubt on whether or not it is an actual issue or not.
We've seen this happen too. It seems the charm sets a default value for is_started[1] to False and never updates that local state to True once the charm is fully configured and active[2].
The fix would be to set that stored value to False in the charm if the status is not active[3] and set it to true if it passes that check[4].
The message is harmless, but it does introduce a measure of doubt on whether or not it is an actual issue or not.
[1]https:/ /github. com/openstack- charmers/ ops-openstack/ blob/master/ ops_openstack/ core.py# L61 /opendev. org/openstack/ charm-cinder- three-par/ src/branch/ master/ src/charm. py#L67- L73 /opendev. org/openstack/ charm-cinder- three-par/ src/branch/ master/ src/charm. py#L70 /opendev. org/openstack/ charm-cinder- three-par/ src/branch/ master/ src/charm. py#L72
[2]https:/
[3]https:/
[4]https:/