Bug 2217471 - [OSP16.1] overcloud deploy recreates all 4 existing compute nodes. [NEEDINFO]
Summary: [OSP16.1] overcloud deploy recreates all 4 existing compute nodes.
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Rabi Mishra
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-26 11:13 UTC by ggrimaux
Modified: 2023-07-18 16:48 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
tkajinam: needinfo? (ggrimaux)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-26046 0 None None None 2023-06-26 11:16:53 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.