Bug 1638002

Summary: genconfig: update old block volumes alua groups from default_tg_pt_gp to glfs_tg_pt_gp
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanna Kumar Kalever <prasanna.kalever>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED ERRATA QA Contact: Rahul Hinduja <rhinduja>
Severity: high Docs Contact:
Priority: high    
Version: ocs-3.11CC: bgoyal, kramdoss, nberry, pkarampu, pprakash, prasanna.kalever, rcyriac, rhs-bugs, sankarshan, suprasad, vbellur, vinug, xiubli
Target Milestone: ---   
Target Release: OCS 3.11   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gluster-block-0.2.1-28.el7rhgs Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-24 04:52:58 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:    
Bug Blocks: 1629581, 1633499, 1637688    

Description Prasanna Kumar Kalever 2018-10-10 13:23:25 UTC 
Description of problem:

Say if, block volumes got created with gluster-block version < 0.2.1-17 (who's alua groups are set to null or default_tg_pt_gp) and after upgrading to OCS >= 3.10 (containing gluster-block >= 0.2.1-27) using them with new multipath.conf (suggested at OCS-3.10) containing alua prio, will break the compatibility

On the initiator side we are noticing messages like:
[...]
sdx: alua not supported
mpathX: failed in domap for addition of new path sdx
[...]


Solution, is to run genconfig. And genconfig should somehow convert default_tg_pt_gp to glfs_tg_pt_gp for fixing this compatibility issue.
Comment 12 errata-xmlrpc 2018-10-24 04:52:58 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, 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/RHEA-2018:2987