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

Bug 2217471

Summary:	[OSP16.1] overcloud deploy recreates all 4 existing compute nodes.
Product:	Red Hat OpenStack	Reporter:	ggrimaux
Component:	openstack-tripleo	Assignee:	Rabi Mishra <ramishra>
Status:	CLOSED NOTABUG	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.1 (Train)	CC:	dhill, jfindysz, jjoyce, jschluet, mburns, ramishra, rurena, slinaber, tvignaud
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-12-20 04:17:32 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 ggrimaux 2023-06-26 11:13:24 UTC

Description of problem:
Client has a small cloud of 4 compute nodes over 2 roles (2 for each).

They run a stack deploy and heat is trying to rebuild all compute nodes with the same names.

From the templates and overcloud plans, the count for each role is 2 so its not scaling out or something like that.
The rebuild fails because there are no new baremetal node to deploy to.

We got a mysqldump from the undercloud.
And a new sosreport from after the deployment attempt.

We need your help to find why heat is trying to do that here.

More info in the next private comment bellow.

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

How reproducible:
100% right now

Steps to Reproduce:
1. do an openstack deploy 
2.
3.

Actual results:
compute nodes are being rebuilt

Expected results:
Overcloud deploy should just not touch actual compute nodes.

Additional info:
we have sosreport and mysqldump of director node.