Description of problem: Migrate to next relese 3.2, it was treated like a v3.1 minor upgrade task by atomic-openshift-installer. Version-Release number of selected component (if applicable): atomic-openshift-utils-3.0.51 How reproducible: always Steps to Reproduce: 1.atomic-openshift-installer -c config/inst120.yaml upgrade 2. 3. Actual results: 1) # atomic-openshift-installer -c config/inst120.yaml upgrade This tool will help you upgrade your existing OpenShift installation. Version 3.1 found. Do you want to update to the latest version of 3.1 or migrate to the next major release? (1) Update to latest 3.1 (2) Migrate to next relese: 2 Openshift will be upgraded from openshift-enterprise 3.1 to openshift-enterprise 3.1 on the following hosts: 2) tailf /tmp/ansible.log 2016-03-07 10:47:03,515 p=32241 u=root | /usr/bin/ansible-playbook --inventory-file=config/.ansible/hosts /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_1_minor/upgrade.yml 2016-03-07 10:47:03,516 p=32241 u=root | 2016-03-07 10:47:03,861 p=32241 u=root | PLAY [Populate config host groups] 2016-03-07 10:47:03,894 p=32241 u=root | TASK: [fail ] ***************************************************************** <--snip---> *************************************************** 2016-03-07 10:47:03,908 p=32241 u=root | fatal: [localhost] => with_items expects a list or a set 2016-03-07 10:47:03,909 p=32241 u=root | FATAL: all hosts have already failed -- aborting 2016-03-07 10:47:03,909 p=32241 u=root | PLAY RECAP ******************************************************************** 2016-03-07 10:47:03,909 p=32241 u=root | to retry, use: --limit @/root/upgrade.retry 2016-03-07 10:47:03,910 p=32241 u=root | localhost : ok=0 changed=0 unreachable=0 failed=1 Expected Result: We can upgrade to v3.2 by atomic-openshift-installer. Additional info:
Was mistaken earlier on call, Sam already has a PR up for this one: https://github.com/openshift/openshift-ansible/pull/1536
It support to upgrade from OSE 3.1 to OSE 3.2 now. so move to verified.
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/RHSA-2016:1064