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

Bug 1652446

Summary:	[Deployment] [Scale] Stack Update fails on scaling out in a Clustered ODL setup
Product:	Red Hat OpenStack	Reporter:	Toni Freger <tfreger>
Component:	openstack-tripleo-heat-templates	Assignee:	Janki <jchhatba>
Status:	CLOSED ERRATA	QA Contact:	Noam Manos <nmanos>
Severity:	high	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	aadam, jchhatba, mariel, mburns, mkolesni, nyechiel, smalleni, vpickard
Target Milestone:	rc	Keywords:	Triaged
Target Release:	14.0 (Rocky)	Flags:	jchhatba: needinfo-
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Deployment
Fixed In Version:	openstack-tripleo-heat-templates-9.0.1-0.20181013060904.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1611960	Environment:	N/A
Last Closed:	2019-01-11 11:55:00 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:
Bug Depends On:	1611960
Bug Blocks:

Comment 4 Janki 2018-11-29 15:22:10 UTC

Moving to ON_DEV as while testing locally with this patch

https://review.openstack.org/#/c/620053/

I successfully scaled out from 1 compute to 2 computes.

Comment 5 Mike Kolesnik 2018-12-12 09:13:40 UTC

Patch has been merged upstream

Comment 19 Noam Manos 2018-12-17 14:21:39 UTC

To verify:

1) Delete the stack: openstack stack delete overcloud --wait --yes

2) In ~/virt/nodes_data.yaml - Change: ComputeCount: 1 

3) Deploy: ./overcloud_deploy.sh

4) Once it is deployed, change in ~/virt/nodes_data.yaml: ComputeCount: 2

5) Redeploy: ./overcloud_deploy.sh

Comment 20 Noam Manos 2018-12-17 20:11:36 UTC

On OSP14 Puddle 2018-12-14.1 scaling out compute has passed successfully.

openstack server list --all
+--------------------------------------+--------------+--------+------------------------+----------------+------------+
| ID                                   | Name         | Status | Networks               | Image          | Flavor     |
+--------------------------------------+--------------+--------+------------------------+----------------+------------+
| b6bde5e4-289e-4e50-9b2f-50876085bd1f | compute-1    | ACTIVE | ctlplane=192.168.24.10 | overcloud-full | compute    |
| 261f79a1-01c4-46e6-977e-d9c72e3b5399 | controller-1 | ACTIVE | ctlplane=192.168.24.18 | overcloud-full | controller |
| 1970064e-e754-46a0-818f-074a0f6a9441 | compute-0    | ACTIVE | ctlplane=192.168.24.11 | overcloud-full | compute    |
| 647203d8-29f1-461a-aafb-c60813a277b7 | controller-0 | ACTIVE | ctlplane=192.168.24.15 | overcloud-full | controller |
| 11f40d9e-581f-4741-a3ac-ed085e7545f3 | controller-2 | ACTIVE | ctlplane=192.168.24.21 | overcloud-full | controller |
+--------------------------------------+--------------+--------+------------------------+----------------+------------+

Comment 24 errata-xmlrpc 2019-01-11 11:55:00 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-2019:0045