Bug 1507246

Summary: Add the ability to have the GlusterFS ansible script run more than once
Product: OpenShift Container Platform Reporter: Alexis Solanas <asolanas>
Component: InstallerAssignee: Jose A. Rivera <jrivera>
Status: CLOSED ERRATA QA Contact: Wenkai Shi <weshi>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.1CC: aos-bugs, bleanhar, dmoessne, fshaikh, javier.ramirez, jokerman, jrivera, mmccomas
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-18 13:23:26 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:

Description Alexis Solanas 2017-10-28 19:28:40 UTC
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:

  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:

Actual results:

 Ansible gluster playbook can only be run once
Expected results:

 Ansible gluster playbook can  be run several times 

Additional info:

Comment 2 Wenkai Shi 2017-11-07 05:45:19 UTC
Verified with version openshift-ansible-3.7.0-0.196.0.git.0.27cd7ec.el7, installer could wait for deploy-heketi pod now.

Comment 3 Javier Ramirez 2017-11-10 12:14:08 UTC
How feasible would be a backport to 3.6 ?

Comment 4 Jose A. Rivera 2017-11-10 12:50:49 UTC
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.

Comment 11 errata-xmlrpc 2017-12-18 13:23:26 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.