Comment 6 for bug 1911909

This piece of pacemaker log seems to be relevant:

Apr 16 12:51:36 juju-d527c3-1-lxd-9 pacemaker-controld[35722]: notice: Node juju-d527c3-1-lxd-9 state is now member
Apr 16 12:51:36 juju-d527c3-1-lxd-9 pacemaker-controld[35722]: notice: Defaulting to uname -n for the local corosync node name
Apr 16 12:51:36 juju-d527c3-1-lxd-9 pacemaker-controld[35722]: notice: Pacemaker controller successfully started and accepting connections
Apr 16 12:51:36 juju-d527c3-1-lxd-9 pacemaker-controld[35722]: notice: State transition S_STARTING -> S_PENDING
Apr 16 12:51:37 juju-d527c3-1-lxd-9 pacemaker-controld[35722]: notice: Fencer successfully connected
Apr 16 12:51:57 juju-d527c3-1-lxd-9 pacemaker-controld[35722]: warning: Input I_DC_TIMEOUT received in state S_PENDING from crm_timer_popped
Apr 16 12:51:57 juju-d527c3-1-lxd-9 pacemaker-controld[35722]: notice: State transition S_ELECTION -> S_INTEGRATION
Apr 16 12:51:58 juju-d527c3-1-lxd-9 pacemaker-schedulerd[35721]: error: Resource start-up disabled since no STONITH resources have been defined
Apr 16 12:51:58 juju-d527c3-1-lxd-9 pacemaker-schedulerd[35721]: error: Either configure some or disable STONITH with the stonith-enabled option
Apr 16 12:51:58 juju-d527c3-1-lxd-9 pacemaker-schedulerd[35721]: error: NOTE: Clusters with shared data need STONITH to ensure data integrity
Apr 16 12:51:58 juju-d527c3-1-lxd-9 pacemaker-schedulerd[35721]: notice: Delaying fencing operations until there are resources to manage
Apr 16 12:51:58 juju-d527c3-1-lxd-9 pacemaker-schedulerd[35721]: notice: Calculated transition 0, saving inputs in /var/lib/pacemaker/pengine/pe-input-2.bz2
Apr 16 12:51:58 juju-d527c3-1-lxd-9 pacemaker-schedulerd[35721]: notice: Configuration errors found during scheduler processing, please run "crm_verify -L" to identify issues