Hide Forgot
Description of problem: Trigger a containerized install by OCP3.2 quick installer, it result in an OCP 3.3 Env. Because openshift-ansible set openshift_version according to openshift3/ose:latest (v3.3.0.34 is tagged as latest) rather than openshift3/ose:v3.2 .There is no version checked in quick-installer so far. # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 09a95933dc14 openshift3/node:v3.3.0.34 "/usr/local/bin/origi" 47 seconds ago Up 39 seconds atomic-openshift-node 4ec8ae3531e4 openshift3/openvswitch:v3.3.0.34 "/usr/local/bin/ovs-r" 3 minutes ago Up 3 minutes openvswitch b6d0d4b74025 openshift3/ose:v3.3.0.34 "/usr/bin/openshift s" 20 minutes ago Up 20 minutes atomic-openshift-master 86af33428e26 registry.access.redhat.com/rhel7/etcd "/usr/bin/etcd" 25 minutes ago Up 25 minutes etcd_container Version-Release number of selected component (if applicable): atomic-openshift-utils-3.2.33-1.git.0.899bad8.el7.noarch How reproducible: always Steps to Reproduce: 1.setup container env by OCP3.2 quick installer # atomic-openshift-installer -c /tmp/installer.cfg.yml install Actual results: It will get wrong version image installed. Expected results: It should set openshift_version according to the version of the qucicker installer.If not, it should do nothing and warn user about no corresponding image. Additional info: If 3.4 release, installer of OCP3.3 should have the same issue.
Workaround is to set openshift_release to the desired value, ie: openshift_release=3.3 in the installer.cfg.yml
Given the workaround in comment 1 i'm lowering the severity of this. We'll need to also make setting the release mandatory once we start shipping a common installer across versions again.