Bug 1656486

Summary: [RFE] GlusterFS version check in installer
Product: OpenShift Container Platform Reporter: Jose A. Rivera <jarrpa>
Component: InstallerAssignee: Jose A. Rivera <jarrpa>
Installer sub component: openshift-ansible QA Contact: Johnny Liu <jialiu>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: gfontana, mgugino
Version: 3.11.0   
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-06 13:11:55 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 2018-12-05 15:41:14 UTC 
For enterprise installations, there should be some mechanism that checks that a user is specifying an explicit version for all OCS container images. It is not simple (nor technically correct) to provide any numbered default to an OCS version per version of openshift-ansible. The only reasonable alternative would be to specify NO default, and require the user to manually specify an explicit version every time (if certain conditions are met, e.g. gluster node groups are defined).
Comment 1 Jose A. Rivera 2018-12-05 15:42:22 UTC 
Michael, can you provide any pointers about where this check should be implemented?
Comment 2 Michael Gugino 2018-12-05 15:57:02 UTC 
I would put it in https://github.com/openshift/openshift-ansible/blob/release-3.11/playbooks/init/sanity_checks.yml

We run that during installs and upgrades.  Gluster-specific plays probably run it as well; this will allow the install/upgrade to fail early.
Comment 3 Jose A. Rivera 2018-12-06 13:11:55 UTC 
It'd help if I searched for duplicates first. :)

*** This bug has been marked as a duplicate of bug 1499035 ***