Comment 13 for bug 1957738

Happened to me as well on an offline deployment...

After more testing, it appears that manila-share service is masked on all manila-ganesha units.
It is consequently required to unmask the service on all of them, otherwise if the leader unit goes down, the whole service is down as well.

  juju run -a manila-ganesha systemctl unmask manila-share

And for Corosync/Pacemaker to try to start right away the service. Doing on one unit :
  juju ssh manila-ganesha/leader sudo crm resource cleanup