| 2022-01-13 04:18:40 |
Yoshi Kadokawa |
bug |
|
|
added bug |
| 2022-01-13 04:31:19 |
Yoshi Kadokawa |
attachment added |
|
pacemaker.log https://bugs.launchpad.net/charm-manila-ganesha/+bug/1957738/+attachment/5553692/+files/pacemaker.log |
|
| 2022-01-13 06:00:46 |
Yoshi Kadokawa |
bug |
|
|
added subscriber Canonical Field High |
| 2022-01-13 06:01:41 |
Yoshi Kadokawa |
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_bdb1339_vip not running"
$ 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 blocked 3 hacluster charmstore stable 81 ubuntu Resource: res_ganesha_bdb1339_vip not running
manila-ganesha 15.2.14 active 3 manila-ganesha charmstore stable 20 ubuntu Unit is ready
manila-ganesha-mysql-router 8.0.27 active 3 mysql-router charmstore stable 15 ubuntu Unit is ready
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-ganesha/2 blocked idle 10.148.197.12 Resource: res_ganesha_bdb1339_vip not running
manila-ganesha-mysql-router/2 active idle 10.148.197.12 Unit is ready
manila-ganesha/1 active idle 7/lxd/7 10.148.197.29 Unit is ready
hacluster-manila-ganesha/1 blocked idle 10.148.197.29 Resource: res_ganesha_bdb1339_vip not running
manila-ganesha-mysql-router/1 active idle 10.148.197.29 Unit is ready
manila-ganesha/2 active idle 8/lxd/7 10.148.197.25 Unit is ready
hacluster-manila-ganesha/0* active executing 10.148.197.25 Unit is ready and clustered
manila-ganesha-mysql-router/0* active idle 10.148.197.25 Unit is ready
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_share_manila_share is also failing.
$ 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_share_manila_share (systemd:manila-share): FAILED juju-a80423-6-lxd-7
* res_nfs_ganesha_nfs_ganesha (systemd:nfs-ganesha): Stopping juju-a80423-6-lxd-7
* Resource Group: grp_ganesha_vips:
* res_ganesha_6cb3ded_vip (ocf::heartbeat:IPaddr2): Started juju-a80423-6-lxd-7
* res_ganesha_959e94a_vip (ocf::heartbeat:IPaddr2): Started juju-a80423-6-lxd-7
* res_ganesha_bdb1339_vip (ocf::heartbeat:IPaddr2): Stopped
Failed Resource Actions:
* res_manila_share_manila_share_start_0 on juju-a80423-6-lxd-7 'error' (1): call=9627, status='complete', exitreason='', last-rc-change='2022-01-13 04:14:14Z', queued=0ms, exec=197ms
For now, I could work around it by executing the following.
$ juju run --unit hacluster-manila-ganesha/leader -- sudo systemctl unmask manila-share
[0] https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/manila-ganesha.html |
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_bdb1339_vip not running"
$ 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 blocked 3 hacluster charmstore stable 81 ubuntu Resource: res_ganesha_bdb1339_vip not running
manila-ganesha 15.2.14 active 3 manila-ganesha charmstore stable 20 ubuntu Unit is ready
manila-ganesha-mysql-router 8.0.27 active 3 mysql-router charmstore stable 15 ubuntu Unit is ready
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-ganesha/2 blocked idle 10.148.197.12 Resource: res_ganesha_bdb1339_vip not running
manila-ganesha-mysql-router/2 active idle 10.148.197.12 Unit is ready
manila-ganesha/1 active idle 7/lxd/7 10.148.197.29 Unit is ready
hacluster-manila-ganesha/1 blocked idle 10.148.197.29 Resource: res_ganesha_bdb1339_vip not running
manila-ganesha-mysql-router/1 active idle 10.148.197.29 Unit is ready
manila-ganesha/2 active idle 8/lxd/7 10.148.197.25 Unit is ready
hacluster-manila-ganesha/0* active executing 10.148.197.25 Unit is ready and clustered
manila-ganesha-mysql-router/0* active idle 10.148.197.25 Unit is ready
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_share_manila_share is also failing.
$ 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_share_manila_share (systemd:manila-share): FAILED juju-a80423-6-lxd-7
* res_nfs_ganesha_nfs_ganesha (systemd:nfs-ganesha): Stopping juju-a80423-6-lxd-7
* Resource Group: grp_ganesha_vips:
* res_ganesha_6cb3ded_vip (ocf::heartbeat:IPaddr2): Started juju-a80423-6-lxd-7
* res_ganesha_959e94a_vip (ocf::heartbeat:IPaddr2): Started juju-a80423-6-lxd-7
* res_ganesha_bdb1339_vip (ocf::heartbeat:IPaddr2): Stopped
Failed Resource Actions:
* res_manila_share_manila_share_start_0 on juju-a80423-6-lxd-7 'error' (1): call=9627, status='complete', exitreason='', last-rc-change='2022-01-13 04:14:14Z', queued=0ms, exec=197ms
For now, I could work around it by executing the following.
$ juju run --unit manila-ganesha/leader -- sudo systemctl unmask manila-share
[0] https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/manila-ganesha.html |
|
| 2022-01-31 15:32:49 |
Felipe Reyes |
charm-manila-ganesha: assignee |
|
Felipe Reyes (freyes) |
|
| 2022-02-02 20:31:53 |
Felipe Reyes |
charm-manila-ganesha: status |
New |
Incomplete |
|
| 2022-02-02 20:32:04 |
Felipe Reyes |
charm-manila-ganesha: assignee |
Felipe Reyes (freyes) |
|
|
| 2022-02-04 02:29:43 |
Yoshi Kadokawa |
charm-manila-ganesha: status |
Incomplete |
New |
|
| 2022-02-04 09:52:28 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
| 2022-02-04 17:17:13 |
Yoshi Kadokawa |
attachment added |
|
juju-crashdump-fa8a94b6-ce4f-4558-9aed-4535f0d05cc6_.tar.gz https://bugs.launchpad.net/charm-manila-ganesha/+bug/1957738/+attachment/5559184/+files/juju-crashdump-fa8a94b6-ce4f-4558-9aed-4535f0d05cc6_.tar.gz |
|
| 2022-02-04 18:31:21 |
Felipe Reyes |
charm-manila-ganesha: status |
New |
Incomplete |
|
| 2022-02-15 10:17:41 |
James Page |
charm-manila-ganesha: status |
Incomplete |
New |
|
| 2022-02-15 10:17:50 |
James Page |
charm-manila-ganesha: status |
New |
Triaged |
|
| 2022-02-15 10:17:52 |
James Page |
charm-manila-ganesha: importance |
Undecided |
High |
|
| 2023-02-02 20:01:40 |
Vern Hart |
bug |
|
|
added subscriber Vern Hart |
| 2023-04-05 18:28:07 |
Peter Mattingly |
bug |
|
|
added subscriber Peter Mattingly |
| 2023-04-12 06:01:15 |
Sysadmin |
bug |
|
|
added subscriber Sysadmin |
| 2023-08-11 12:49:12 |
Bayani Carbone |
bug |
|
|
added subscriber Bayani Carbone |
| 2023-09-06 15:30:30 |
Bas de Bruijne |
bug |
|
|
added subscriber Bas de Bruijne |
