hacluster for manila-ganesha get stuck with "Resource: res_ganesha_xxx_vip not running"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Manila-Ganesha Charm |
Triaged
|
High
|
Unassigned |
Bug Description
I have deployed manila and manila-ganesha both in 3 LXD units with hacluster, as described in the official document[0].
However, the hacluster charm status get stuck with a message of "Resource: res_ganesha_
$ juju status manila-ganesha
Model Controller Cloud/Region Version SLA Timestamp
openstack foundations-maas maas_cloud 2.9.22 unsupported 04:08:40Z
App Version Status Scale Charm Store Channel Rev OS Message
hacluster-
manila-ganesha 15.2.14 active 3 manila-ganesha charmstore stable 20 ubuntu Unit is ready
manila-
Unit Workload Agent Machine Public address Ports Message
manila-ganesha/0* active idle 6/lxd/7 10.148.197.12 Unit is ready
hacluster-
manila-
manila-ganesha/1 active idle 7/lxd/7 10.148.197.29 Unit is ready
hacluster-
manila-
manila-ganesha/2 active idle 8/lxd/7 10.148.197.25 Unit is ready
hacluster-
manila-
Machine State DNS Inst id Series AZ Message
6 started 10.148.196.229 controller-node-1 focal zone1 Deployed
6/lxd/7 started 10.148.197.12 juju-a80423-6-lxd-7 focal zone1 Container started
7 started 10.148.196.237 controller-node-5 focal zone2 Deployed
7/lxd/7 started 10.148.197.29 juju-a80423-7-lxd-7 focal zone2 Container started
8 started 10.148.196.235 controller-node-3 focal zone3 Deployed
8/lxd/7 started 10.148.197.25 juju-a80423-8-lxd-7 focal zone3 Container started
And here is the output from pacemaker. As you can see not just the res_ganesha_xxx_vip but also res_manila_
$ sudo crm status
Cluster Summary:
* Stack: corosync
* Current DC: juju-a80423-8-lxd-7 (version 2.0.3-4b1f869f0f) - partition with quorum
* Last updated: Thu Jan 13 04:14:17 2022
* Last change: Thu Jan 13 04:14:13 2022 by root via crm_node on juju-a80423-6-lxd-7
* 3 nodes configured
* 5 resource instances configured
Node List:
* Online: [ juju-a80423-6-lxd-7 juju-a80423-7-lxd-7 juju-a80423-8-lxd-7 ]
Full List of Resources:
* res_manila_
* res_nfs_
* Resource Group: grp_ganesha_vips:
* res_ganesha_
* res_ganesha_
* res_ganesha_
Failed Resource Actions:
* res_manila_
For now, I could work around it by executing the following.
$ juju run --unit manila-
[0] https:/
description: | updated |
I have attached the log of pacemaker as well.
In this log, I could see that the pacemaker resource is failing with the following error.
Could not issue start for res_manila_ share_manila_ share: Unit manila- share.service is masked.
This symptom is seen every time I deploy this environment.
BTW, since Vault is used as TLS termination for API endpoints, the reproducible steps are
1. Deploy OpenStack with Vault manila- ganesha is all fine manila- ganesha gets stuck. I have waited for more than 30 minutes, but it was still stuck.
2. Unlock and activate Vault. Before this, hacluster-
3. After the relation with Vault is completed, hacluster-