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

Bug 1436728

Summary:	How to avoid restart of services on controller nodes during compute scaleout
Product:	Red Hat OpenStack	Reporter:	VIKRANT <vaggarwa>
Component:	puppet-tripleo	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	aschultz, jjoyce, jschluet, slinaber, tvignaud
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-28 14:42: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:

Description VIKRANT 2017-03-28 14:04:37 UTC

Description of problem:

To avoid service restart on controller nodes during compute scaleout

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

RHEL OSP 10
puppet-tripleo-5.5.0-4.el7ost.noarch

How reproducible:
Everytime. 

Steps to Reproduce:
1. Deploy a overcloud setup. Note down the pid of processes. 
2. Try to perform the scale out of compute node. 
3. Process id of most processes on controller node got changed that means services got restarted. 

Actual results:
Services are getting restarted on controller node. 

Expected results:
Service shouldn't get restarted on controller nodes during scaleout. 

Additional info:

More information is coming in internal comments.

Comment 2 Alex Schultz 2017-03-28 14:42:38 UTC


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