Bug 1935798

Summary: pacemaker on google cloud: gcp-pd-move do not handle correctly disks when disk_scope="regional" (RHEL7)
Product: Red Hat Enterprise Linux 7 Reporter: Andrea Perotti <aperotti>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: Brandon Perkins <bperkins>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.9CC: agk, bperkins, cfeist, cluster-maint, fdinitto, jreznik, sbradley
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: resource-agents-4.1.1-61.el7_9.11 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1935804 (view as bug list) Environment:
Last Closed: 2021-06-08 22:29:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1890068    
Bug Blocks: 1935804    

Description Andrea Perotti 2021-03-05 15:30:46 UTC 
Description of problem:

When deploying a pacemaker cluster on RHEL7, and gcp-pd-move resource is used, when "disk_scope" parameter is set to "regional" then the disk not attach.

Version-Release number of selected component (if applicable):
resource-agents-gcp-4.1.1-61.el7_9.5.x86_64                 Fri Mar  5 10:47:21 2021


How reproducible:
Always


Actual results:
disk not attach in gcp-pd-move resource.

gcp-pd-move: INFO: Attaching disk gcp-rh7-disk1 to gcp-rh7-n1
lrmd[1766]:  notice: p_gcp-rh7-disk1_start_0:2505:stderr [ INFO:gcp-pd-move:Attaching disk gcp-rh7-disk1 to gcp-rh7-n1 ]
lrmd[1766]:  notice: p_gcp-rh7-disk1_start_0:2505:stderr [   File "/usr/lib/ocf/resource.d/heartbeat/gcp-pd-move", line 377, in <module> ]
lrmd[1766]:  notice: p_gcp-rh7-disk1_start_0:2505:stderr [   File "/usr/lib/ocf/resource.d/heartbeat/gcp-pd-move", line 366, in main ]
lrmd[1766]:  notice: p_gcp-rh7-disk1_start_0:2505:stderr [   File "/usr/lib/ocf/resource.d/heartbeat/gcp-pd-move", line 331, in gcp_pd_move_start ]
lrmd[1766]:  notice: p_gcp-rh7-disk1_start_0:2505:stderr [   File "/usr/lib/ocf/resource.d/heartbeat/gcp-pd-move", line 316, in attach_disk ]
crmd[1769]:  notice: gcp-rh7-n1-p_gcp-rh7-disk1_start_0:44 [ INFO:gcp-pd-move:Attaching disk gcp-rh7-disk1 to gcp-rh7-n1\nTraceback (most recent call last):\n  File "/usr/lib/ocf/resource.d/heartbeat/gcp-pd-move", line 377, in <module>\n    main()\n  File "/usr/lib/ocf/resource.d/heartbeat/gcp-pd-move", line 366, in main\n    gcp_pd_move_start()\n  File "/usr/lib/ocf/resource.d/heartbeat/gcp-pd-move", line 331, in gcp_pd_move_start\n    attach_disk(INSTANCE_NAME, PARAMETERS['disk_name'])\n  File "/usr/lib


Additional info:

The change is minimal, but make huge difference for the customers who are moving their clustered workloads to Google Cloud.

The issue has been fixed in upstream https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/gcp-pd-move.in :

+  if PARAMETERS['disk_scope'] == 'regional':
+    location = 'regions/%s' % REGION
Comment 10 errata-xmlrpc 2021-06-08 22:29:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (resource-agents bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:2311