Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1279734

Summary: The service status is disabled after upgrade
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: Cluster Version OperatorAssignee: Devan Goodwin <dgoodwin>
Status: CLOSED ERRATA QA Contact: Johnny Liu <jialiu>
Severity: high Docs Contact:
Priority: high    
Version: 3.0.0CC: aos-bugs, bleanhar, dgoodwin, jokerman, mmccomas
Target Milestone: ---Flags: anli: needinfo-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-ansible-3.0.9-1.git.0.9f97293.el7aos Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 23:29:26 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 Anping Li 2015-11-10 07:31:13 UTC
Description of problem:
After upgrade openshift from v3.0.2.0 to v3.1, the service for atomic-openshift-* was disabled.  The openshift will be out of service after reboot.

Version-Release number of selected component (if applicable):
openshift-ansible-playbooks-3.0.7-1.git.156.70ed54c.el7aos.noarch

How reproducible:
always

Steps to Reproduce:
1. upgrade to v3.1
2. check the service status  on master and nodes

Actual results:
[root@openshift-120 ~]# systemctl status atomic-openshift-master
atomic-openshift-master.service - Atomic OpenShift Master
   Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-master.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: https://github.com/openshift/origin

[root@openshift-136 ~]# systemctl status atomic-openshift-node
atomic-openshift-node.service - Atomic OpenShift Node
   Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-node.service; disabled)
  Drop-In: /usr/lib/systemd/system/atomic-openshift-node.service.d
           └─openshift-sdn-ovs.conf
   Active: inactive (dead)
     Docs: https://github.com/openshift/origin


Expected results:
the service should be enabled after upgrade.

Additional info:

Comment 1 Devan Goodwin 2015-11-10 19:54:38 UTC
Fixed as of 28d601beeebaacd5e79b3fec336a283c8bf20e68

Comment 3 Anping Li 2015-11-11 14:54:26 UTC
The service  status is still disabled, Can you check if the fix was merged in to  openshift-ansible-bin-3.0.7-1.git.174.4c1b0dd.el7.noarch?

Comment 5 Anping Li 2015-11-12 03:58:10 UTC
Verified and pass on atomic-openshift-utils-3.0.12-1

Comment 7 errata-xmlrpc 2015-11-19 23:29:26 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/RHEA-2015:2492