Description of problem: Remove 3.1, 3.0 and AEP from atomic-openshift-installer due to atomic-openshift-utils 3.2 don't support. Version-Release number of selected component (if applicable): OSE 3.2 atomic-openshift-utils-3.2.13 How reproducible: always Steps to Reproduce: 1. atomic-openshift-installer install 2. 3. Actual results: It prompt we can installed 3.1, 3.0 and AEP, In fact, installer will fail. #atomic-openshift-installer install Welcome to the OpenShift Enterprise 3 installation. Please confirm that following prerequisites have been met: <--skip--> Which variant would you like to install? (1) OpenShift Enterprise 3.2 (2) OpenShift Enterprise 3.1 (3) OpenShift Enterprise 3.0 (4) Atomic Enterprise Platform 3.2 (5) Atomic Enterprise Platform 3.1 Choose a variant from above: [1]: 2 <--skip---> <--skip---> TASK: [docker | Get current installed Docker version] ************************* ok: [host4master.example.com] TASK: [docker | Error out if Docker pre-installed but too old] **************** failed: [host4master.example.com] => {"failed": true} msg: Docker 1.8.2 is installed, but >= 1.9.1 is required. FATAL: all hosts have already failed -- aborting PLAY RECAP ******************************************************************** to retry, use: --limit @/root/config.retry host4master.example.com : ok=132 changed=15 unreachable=0 failed=1 host4node.example.com : ok=48 changed=2 unreachable=0 failed=0 localhost : ok=12 changed=0 unreachable=0 failed=0 Expected results: Additional info:
Opened https://github.com/openshift/openshift-ansible/pull/2242 to address this.
We need to build a new RPM packge w/ above patch in Comment 1, because the issue hasn't been fixed in atomic-openshift-utils-3.2.13-1.git.0.0afa976.el7.noarch.
Those options are removed at atomic-openshift-utils-3.2.18-1.git.0.2015d79.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:1639