Bug 1320951

Summary: The IMAGE_VERSION isn't correct when upgrade the containerized OSE
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: Cluster Version OperatorAssignee: Brenton Leanhardt <bleanhar>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: high    
Version: 3.2.0CC: aos-bugs, bleanhar, jokerman, mmccomas, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-ansible-3.0.67-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-12 16:34:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Upgrade failed due to the IMGAGE_VESION are set to 'v' none

Description Anping Li 2016-03-24 10:58:17 UTC 
Description of problem:
The IMAGE_VERSION was set to 'IMAGE_VERSION=v' in the system configure files. it is wrong,  it should like 'v3.1.16'.

OPTIONS=--loglevel=2
CONFIG_FILE=/etc/origin/node/node-config.yaml
IMAGE_VERSION=v


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.0.64

How reproducible:
always

Steps to Reproduce:
1. install ose3.1 on atomic hosts
2. upgrade to ose3.2 using ansible-playbook

Actual results:
The upgrade failed due the IMAGE_VERSION is 'v' in the atomic hosts

cat atomic-openshift-node

OPTIONS=--loglevel=2
CONFIG_FILE=/etc/origin/node/node-config.yaml
IMAGE_VERSION=v


Expected results:
It should be set to correct values before upgrade. for example: v3.1.1.6

Additional info:
Comment 1 Anping Li 2016-03-24 11:00:27 UTC 
Created attachment 1139899 [details]
Upgrade failed due to the IMGAGE_VESION are set to 'v'
Comment 2 Brenton Leanhardt 2016-03-28 20:55:34 UTC 
I should be able to have this ON_QA tomorrow.
Comment 4 Anping Li 2016-03-30 07:55:02 UTC 
The image version is correct now. so move bug to verified.
Comment 6 errata-xmlrpc 2016-05-12 16:34:11 UTC 
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