Bug 971397

Summary:	[upgrade]openshift-console service is not enabled by chkconfig
Product:	OpenShift Container Platform	Reporter:	Johnny Liu <jialiu>
Component:	Node	Assignee:	John W. Lamb <jolamb>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.2.0	CC:	bleanhar, gpei, jolamb, libra-onpremise-devel
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-28 15:47:13 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:

Description Johnny Liu 2013-06-06 12:31:43 UTC

Description of problem:
After upgrade, openshift-console service is not enabled by chkconfig.

Version-Release number of selected component (if applicable):
1.2/2013-06-05.9

How reproducible:
Always

Steps to Reproduce:
1. Setup ose-1.1.3 env
2. Make sure openshift-console is enabled by chkconfig
3. Following http://etherpad.corp.redhat.com/OSE-1-2-upgrade-notes to do upgrade testing
4. After upgrade, check if openshift-console is enabled by chkconfig

Actual results:
openshift-console is not enabled

Expected results:
openshift-console should be enabled.

Additional info:

Comment 2 Luke Meyer 2013-06-06 20:42:31 UTC

Good catch, needs to be added to broker conf steps.

I think what happened is openshift-origin-console obsoleted openshift-console. When the latter was removed it removed the openshift-console service. Then when the former was added it doesn't chkconfig on by default, need to do that explicitly.

Comment 3 John W. Lamb 2013-06-07 20:37:59 UTC

Customers may want the console disabled; the most correct behavior would be to check if openshift-console is chkconfig on prior to the upgrade, then restore that state during upgrade completion.

Comment 4 John W. Lamb 2013-06-11 20:02:33 UTC

This bug has been addressed with this merge: https://github.com/openshift/enterprise/commit/31fb35f9a2769a29b3d94f6f3107e377f2634daa

Comment 5 Gaoyun Pei 2013-06-14 07:43:48 UTC

Verify this against puddle:
http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.2/2013-06-13.1/

Setup an OSE env using puddle 1.1.z/2013-06-11.2. Then update this env to puddle 1.2/2013-06-13.1.
Check the status of openshift-console service using chkconfig
[root@broker ~]# chkconfig --list openshift-console
openshift-console	0:off	1:off	2:on	3:on	4:on	5:on	6:off

The 2/3/4/5 level are all set as on, so verify this bug.

Comment 6 Luke Meyer 2013-06-28 15:47:13 UTC

Closing all bugs introduced, fixed, and verified during 1.2 release work (thus never shipped).