Hide Forgot
Description of problem: atomic-openshift-installer generate wrong variant_version in installer.cfg.yml. Version-Release number of the following components: atomic-openshift-utils-3.7.0-0.190.0.git.0.129e91a.el7 How reproducible: 100% Steps to Reproduce: 1. Use quick installer. # atomic-openshift-installer install 2. Check installer.cfg.yml. # grep "3.6" .config/openshift/installer.cfg.yml variant_version: '3.6' 3. Actual results: # grep "3.6" .config/openshift/installer.cfg.yml variant_version: '3.6' Expected results: Should be 3.7 Additional info: May some other variables need to fix: # grep -nir "3.6" /usr/lib/python2.7/site-packages/ooinstall/ /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py:37: 'major_playbook': 'v3_6/upgrade.yml', /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py:38: 'major_version': '3.6', /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py:40: '3.6': { /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py:41: 'minor_version': '3.6', /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py:42: 'minor_playbook': 'v3_6/upgrade.yml', /usr/lib/python2.7/site-packages/ooinstall/variants.py:42: Version('3.6', 'openshift-enterprise'), /usr/lib/python2.7/site-packages/ooinstall/variants.py:46: Version('3.6', 'openshift-enterprise', 'registry'), /usr/lib/python2.7/site-packages/ooinstall/variants.py:50: Version('3.6', 'origin'),
Modify the variant_version to 3.7, met this: # atomic-openshift-installer -u install openshift-enterprise 3.7 is not an installable variant. # tail -3 .config/openshift/installer.cfg.yml variant: openshift-enterprise variant_version: '3.7' version: v2
https://github.com/openshift/openshift-ansible/pull/6274 adds v3.7 support to the quick installer
Verified with version openshift-ansible-3.7.9-1.git.35.36453c1.el7. The variant_version in installer.cfg.yml is 3.7 now. # tail -3 .config/openshift/installer.cfg.yml variant: openshift-enterprise variant_version: '3.7' version: v2
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:3280