Description of problem: === OpenShift Quick Installation failed due to variant_version mismatch Version-Release number of selected component (if applicable): === Upgrade 3.2 to 3.3 (atomic-openshift-utils-3.3.22-1.git.0.6c888c2.el7.noarch) How reproducible: === Steps to Reproduce: 1. Set variant_version as "3.2" and configure as [1] 2. Run "atomic-openshift-installer upgrade" Actual results: === Getting error: TASK [openshift_version : fail] ************************************************ fatal: [knakayam-ose32-smaster.example.com]: FAILED! => {"changed": false, "failed": true, "msg": "Detected OpenShift version 3.3.0.32 does not match requested openshift_release 3.2. You may need to adjust your yum repositories, inventory, or run the appropriate OpenShift upgrade playbook."} Expected results: Upgrade successed without error Additional info: === If I set "variant_version" as '3.3', installer doesn't start at all. [1] --- ansible_callback_facts_yaml: /root/.config/openshift/.ansible/callback_facts.yaml ansible_config: /usr/share/atomic-openshift-utils/ansible.cfg ansible_inventory_path: /root/.config/openshift/hosts ansible_log_path: /tmp/ansible.log deployment: ansible_ssh_user: root hosts: - connect_to: knakayam-ose32-smaster.example.com hostname: knakayam-ose32-smaster.example.com ip: xx.xx.xx.xx public_hostname: knakayam-ose32-smaster.example.com public_ip: xx.xx.xx.xx roles: - master - node master_routingconfig_subdomain: '' proxy_exclude_hosts: '' proxy_http: '' proxy_https: '' roles: master: {} node: {} variant: openshift-enterprise variant_version: '3.2' version: v2
Commit pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/ff02f9999299d69b7984ee99e81f3fff24afa7a7 Fix upgrade mappings in quick installer Update to use the correct playbook for 3.2 to 3.3 upgrades and some error handling for unsupported upgrades. Fixes Bug 1381411
Verified and pass with atomic-openshift-utils-3.3.37-1.git.0.10ff25b.el7.noarch
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-2016:2122