PR created in master: https://github.com/openshift/openshift-ansible/pull/10137
Also, you need to specify glusterfs_ip for each glusterfs_registry host.
Referened PR is merged into release-3.11 already.
Verified with: openshift-ansible-3.11.38-1.git.0.d146f83.el7.noarch TASK [openshift_node : Install GlusterFS storage plugin dependencies] **************************************************************************************** task path: /usr/share/ansible/openshift-ansible/roles/openshift_node/tasks/glusterfs.yml:2 ok: [qe-piqin-4-master-etcd-1.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.13.2-2.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-node-registry-router-1.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-node-1.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-glusterfs-registry-node-2.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-glusterfs-registry-node-1.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]} ok: [qe-piqin-4-glusterfs-registry-node-3.1104-6kt.qe.rhcloud.com] => {"attempts": 1, "changed": false, "msg": "", "rc": 0, "results": ["glusterfs-fuse-3.12.2-18.el7.x86_64 providing glusterfs-fuse is already installed"]}
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/RHBA-2018:3537