Bug 1376803

Summary:	openshift-enterprise-release is not upgraded after upgrading to OSE 2.2.10
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	Installer	Assignee:	Jason DeTiberus <jdetiber>
Status:	CLOSED ERRATA	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.2.0	CC:	ahardin, aos-bugs, jokerman, mmccomas, rthrashe
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The openshift-enterprise-update package was not updated for 2.2.10 Consequence: OpenShift will show as being on 2.2.9, despite being updated to 2.2.10. This can cause problems with supporting customers as support will have the wrong version information. Fix: Update the openshift-enterprise-upgrade package. Result: OpenShift will now recognize that it is on the correct version, 2.2.10.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-20 20:26:31 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:

Description Jaspreet Kaur 2016-09-16 12:31:07 UTC

Description of problem: After following the steps mentioned here :

https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/2.2_Release_Notes/index.html#Upgrading_to_OpenShift_Enterprise_2.2

The file for release is not updated even following the steps.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
 	After running the yum update command on each host and ensuring all packages have been updated, restart ActiveMQ on any broker or messaging host running the service:

# service activemq restart

Restart the ruby193-mcollective service on each node host:

# service ruby193-mcollective restart

On the broker host, restart the broker service and, if installed, the Management Console service:

# service openshift-broker restart
# service openshift-console restart

Restart the routing daemon, if installed and integrated with F5 BIG-IP LTM®:

# service openshift-routing-daemon restart

On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.

# oo-admin-ctl-cartridge -c import-profile --activate --obsolete
# oo-admin-ctl-cartridge -c migrate

On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other oo-admin-upgrade command usage and use 2.2.10 as the target --version.

# oo-admin-upgrade archive
# oo-admin-upgrade upgrade-node --version=2.2.10

Actual results: The file is not updated.


Expected results: The file should have updated to provide the correct result.


Additional info:

Comment 4 Rory Thrasher 2016-09-16 20:37:06 UTC

QA,

Can we verify that this has been updated with the following puddle?

Puddle: http://etherpad.corp.redhat.com/puddle-2-2-2016-09-16

Please check that the /etc/openshift-enterprise-release file contains 2.2.10 rather than 2.2.9.

Comment 5 Johnny Liu 2016-09-18 02:28:01 UTC

Verified this bug with OpenShiftEnterpriseErrata/2.2/2016-09-16.1, and PASS.

# yum update
# cat /etc/openshift-enterprise-release 
OpenShift Enterprise 2.2.10

Comment 7 errata-xmlrpc 2016-09-20 20:26:31 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://rhn.redhat.com/errata/RHBA-2016-1911.html