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

Bug 1416083

Summary: During OSP 9 =>10 upgrade, openstack services moved out of pacemaker are not enabled via systemd
Product: Red Hat OpenStack Reporter: Chris Paquin <cpaquin>
Component: rhosp-directorAssignee: Angus Thomas <athomas>
Status: CLOSED DUPLICATE QA Contact: Amit Ugol <augol>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: augol, dbecker, mburns, morazi, rhel-osp-director-maint, sbaker, shardy, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-24 14:47:38 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:
Attachments:
Description Flags
Services on Upgraded Controller none

Description Chris Paquin 2017-01-24 14:30:57 UTC
Created attachment 1243941 [details]
Services on Upgraded Controller

Description of problem:
Following the step that includes  "-e /home/stack/templates/environments/major-upgrade-pacemaker.yaml."

Services are removed from pacemaker control, but are not enabled via systemd as they should be.

However, these services are not being enabled via systemd as they should be.


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

How reproducible:
Upgrade from OSP 9 to 10. 

Steps to Reproduce:
1. Follow upgrade guide for OSP 10
2. Run upgrade step with /home/stack/templates/environments/major-upgrade-pacemaker.yaml.
3. Log into controller run the following "systemctl list-unit-files | grep openstack"

Actual results:
Services are removed from pacemaker control but are not enabled.

Expected results:
Openstack services should be set to enabled 

Additional info:

Comment 1 Chris Paquin 2017-01-24 14:47:38 UTC

*** This bug has been marked as a duplicate of bug 1416073 ***