Description of problem: Currently it's not possible to run the ansible scripts more than once, or to updated the gluster topology once the cluster is running. The following upstream PR solves this issues: https://github.com/openshift/openshift-ansible/pull/5415 Version-Release number of the following components: openshift-ansible-3.6.173.0.48-1.git.0.1609d30.el7.noarch ansible-2.3.1.0-3.el7.noarch ansible 2.3.1.0 config file = /etc/ansible/ansible.cfg configured module search path = Default w/o overrides python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)] How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Ansible gluster playbook can only be run once Expected results: Ansible gluster playbook can be run several times Additional info:
Verified with version openshift-ansible-3.7.0-0.196.0.git.0.27cd7ec.el7, installer could wait for deploy-heketi pod now.
How feasible would be a backport to 3.6 ?
Using openshift-ansible to deploy GlusterFS is not recommended in 3.6 since the playbooks are out of date. I would say we should not bother backporting this fix.
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-2017:3464