Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1326642 - The IMAGE_VERSION is not the value we specified by openshift_image_tag
The IMAGE_VERSION is not the value we specified by openshift_image_tag
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.2.0
Unspecified Unspecified
high Severity medium
: ---
: ---
Assigned To: Devan Goodwin
Anping Li
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-13 05:26 EDT by Anping Li
Modified: 2016-06-07 06:55 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-07 06:55:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1208 normal SHIPPED_LIVE Red Hat OpenShift Enterprise atomic-openshift-utils bug fix update 2016-06-07 10:55:01 EDT

  None (edit)
Description Anping Li 2016-04-13 05:26:28 EDT
Description of problem:
Openshift ansible is using g_aos_versions.avail_version to set VERSION in sysconfig files. however, if we specify openshift_image_tag, the target version values is stored in g_new_version.


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.0.79-1.git.0.9c75f11.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. install containerlized OSE 3.1
2. set openshift_image_tag to a value which is different with the latest in inventory file
   For example: if openshift3/ose:latest=openshift3/ose:v3.2.0.14, we set openshift_image_tag=v3.2.0.12
3. upgrade to OSE3.2 using ansible-playbook
4. check the VERSION under /etc/sysconfig/atomic-openshift-* /etc/sysconfig/openvswitch
   grep VERSION /etc/sysconfig/atomic-openshift* /etc/sysconfig/openvswitch


Actual results:
4. grep VERSION /etc/sysconfig/atomic-openshift* /etc/sysconfig/openvswitch
/etc/sysconfig/atomic-openshift-master:IMAGE_VERSION=v3.2.0.14
/etc/sysconfig/atomic-openshift-master-api:IMAGE_VERSION=v3.2.0.14
/etc/sysconfig/atomic-openshift-master-controllers:IMAGE_VERSION=v3.2.0.14
/etc/sysconfig/atomic-openshift-node:IMAGE_VERSION=v3.2.0.14
/etc/sysconfig/openvswitch:IMAGE_VERSION=v3.2.0.14



Expected results:
The IMAGE_VERSION should be same with openshift_image_tag

Additional info:
Comment 1 Anping Li 2016-04-13 07:14:00 EDT
please also notice that openshift_container_versions.sh was ran before docker new options take affect. so we couldn't get the VERSION from the new added registry.
Comment 2 Devan Goodwin 2016-04-18 14:17:08 EDT
I think this is still happening even using latest master and Sam's branch.

Using a private registry with 3.2.0.14 and 3.2.0.16 pushed to it, and in my inventory:

openshift_image_tag=v3.2.0.14

After running upgrade:

bash-4.2# grep VERSION /etc/sysconfig/atomic-openshift* /etc/sysconfig/openvswitch
/etc/sysconfig/atomic-openshift-master:IMAGE_VERSION=v3.2.0.16
/etc/sysconfig/atomic-openshift-node:IMAGE_VERSION=v3.2.0.16
/etc/sysconfig/openvswitch:IMAGE_VERSION=v3.2.0.16
Comment 3 Devan Goodwin 2016-04-20 13:42:05 EDT
Fixed and merged in: https://github.com/openshift/openshift-ansible/pull/1781
Comment 5 Anping Li 2016-05-17 03:54:32 EDT
The bug fixed, so moved to verified.
Comment 7 errata-xmlrpc 2016-06-07 06:55:17 EDT
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:1208

Note You need to log in before you can comment on or make changes to this bug.