The bug appears to originate from interface-hacluster. There was recent work to prevent pacemaker from giving up on stopped resources[1]. However, when it was merged[2], the same fix was not applied to the SystemdService class that had also been introduced by another recent commit.
We're using the SystemdService class, and it's missing that fix. Once a resource is stopped, it stays stopped.
As a workaround, it looks like you can manually clear the stopped resource by running the cleanup action:
The bug appears to originate from interface- hacluster. There was recent work to prevent pacemaker from giving up on stopped resources[1]. However, when it was merged[2], the same fix was not applied to the SystemdService class that had also been introduced by another recent commit.
We're using the SystemdService class, and it's missing that fix. Once a resource is stopped, it stays stopped.
As a workaround, it looks like you can manually clear the stopped resource by running the cleanup action:
juju run-action hacluster/0 cleanup --wait
[1]: https:/ /github. com/openstack/ charm-interface -hacluster/ commit/ fe9d009520be508 2f82ff99bce8d46 0a02bd7c93 /github. com/openstack/ charm-interface -hacluster/ commit/ 38590837dae187a 96f092236aeda61 c8b2fda7cc
[2]: https:/