Bug 1320951 - The IMAGE_VERSION isn't correct when upgrade the containerized OSE
Summary: The IMAGE_VERSION isn't correct when upgrade the containerized OSE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Brenton Leanhardt
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-24 10:58 UTC by Anping Li
Modified: 2016-05-12 16:34 UTC (History)
5 users (show)

Fixed In Version: openshift-ansible-3.0.67-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 16:34:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Upgrade failed due to the IMGAGE_VESION are set to 'v' (24.30 KB, text/plain)
2016-03-24 11:00 UTC, Anping Li
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1064 0 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 3.2 security, bug fix, and enhancement update 2016-05-12 20:19:17 UTC

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


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