Red Hat Bugzilla – Bug 971397
[upgrade]openshift-console service is not enabled by chkconfig
Last modified: 2017-03-08 12:35 EST
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:
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.
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.
This bug has been addressed with this merge: https://github.com/openshift/enterprise/commit/31fb35f9a2769a29b3d94f6f3107e377f2634daa
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.
Closing all bugs introduced, fixed, and verified during 1.2 release work (thus never shipped).