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.
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