Description of problem: When migrating openshift from 3.2.1.17 to 3.3.0.32 by setting the openshift_pkg_version=-3.3.0.32 using ansible installer : ansible-playbook -i /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_3/upgrade.yml It still upgrades to v 3.3.0.35 The result after migration + reboot : [root@cdyi0538 ~]# openshift version openshift v3.3.0.35 kubernetes v1.3.0+52492b4 etcd 2.3.0+git Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Migrated to incorrect version Expected results: It should have helped to migrate to correct version. Additional info:
Hi, raising the priority of the case, due the bug is causing unwanted/untested release deployed on production systems ( for customer ). Customer is running tests on latest version, but during the time new release is released. Thx
https://github.com/openshift/openshift-ansible/pull/4119
atomic-openshift-utils-3.5.69-1.git.0.61edbcb.el7.noarch OCP can be upgraded from v3.4 to v3.5.5.5 when specified openshift_pkg_version=-3.5.5.5 OCP can be upgraded from v3.5.5.6 to v3.5.5.8 when specified openshift_pkg_version=-3.5.5.8. So move bug 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-2017:1244