Bug 1512978

Summary: [3.7] Fix support for CNS deployment
Product: OpenShift Container Platform Reporter: Jose A. Rivera <jarrpa>
Component: InstallerAssignee: Jose A. Rivera <jarrpa>
Status: CLOSED ERRATA QA Contact: Wenkai Shi <weshi>
Severity: urgent Docs Contact:
Priority: high    
Version: 3.7.0CC: aos-bugs, jokerman, mmccomas, pprakash, smunilla
Target Milestone: ---   
Target Release: 3.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
This BZ brings new features to the GlusterFS deployments, in particular the ability to provision glusterblock and gluster-s3 volumes.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-18 13:23:56 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:

Description Jose A. Rivera 2017-11-14 14:37:14 UTC
The following PR needs to make it into OCP 3.7 ASAP, likely as an async advisory:

https://github.com/openshift/openshift-ansible/pull/5784

Without this PR, the OCP 3.7 openshift-ansible installer will have no ability to properly deploy CNS 3.6 or CNS 3.7.

Comment 1 Scott Dodson 2017-11-15 19:11:53 UTC
Here's a test build with Jose's fixes for CNS 3.6, we'll merge these changes into release-3.7 after it's been smoke tested and after 3.7 GA regression testing has completed.

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=625394

Comment 4 Wenkai Shi 2017-11-28 04:23:53 UTC
This is block by BZ #1517225

Comment 11 Wenkai Shi 2017-12-11 10:02:11 UTC
Verified with version atomic-openshift-3.7.14-1.git.0.593a50e.el7, codes all merged. 
QE has tested full CNS/CRS deployment, all works well except gluster-s3. (BZ #1518108)
For standalone deployment, playbooks/byo/openshift-glusterfs/config.yml works well will document update (BZ #1520272 BZ #1520342), playbooks/byo/openshift-glusterfs/registry.yml still has issue. (BZ #1524342)

Comment 14 errata-xmlrpc 2017-12-18 13:23:56 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/RHBA-2017:3464