Back to bug 2092444

Who When What Removed Added
Red Hat One Jira (issues.redhat.com) 2022-06-01 14:57:33 UTC Link ID Red Hat Issue Tracker OSP-15472
Brendan Shephard 2022-06-01 22:48:24 UTC CC bshephar
Steve Baker 2022-06-06 19:43:54 UTC Flags needinfo?(drosenfe)
CC sbaker
Steve Baker 2022-06-06 19:44:42 UTC QA Contact drosenfe jhakimra
Component openstack-tripleo-common tripleo-ansible
Assignee apetrich sbaker
Keywords Triaged
Steve Baker 2022-06-06 19:45:09 UTC Status NEW ASSIGNED
David Rosenfeld 2022-06-14 17:05:11 UTC Flags needinfo?(drosenfe)
Steve Baker 2022-06-15 01:48:15 UTC Flags needinfo?(drosenfe)
David Rosenfeld 2022-06-15 16:55:45 UTC Flags needinfo?(drosenfe)
Steve Baker 2022-06-15 21:50:05 UTC Status ASSIGNED ON_DEV
Link ID OpenStack gerrit 846067
Steve Baker 2022-06-19 22:15:46 UTC Link ID OpenStack gerrit 846531
Priority unspecified high
Steve Baker 2022-06-19 22:16:37 UTC Target Release --- 17.0
Target Milestone --- beta
Steve Baker 2022-06-19 22:16:57 UTC Component tripleo-ansible python-metalsmith
Assignee sbaker dtantsur
QA Contact jhakimra
Steve Baker 2022-06-20 23:23:11 UTC Assignee dtantsur sbaker
Steve Baker 2022-06-21 21:57:37 UTC Link ID OpenStack gerrit 846067
Steve Baker 2022-06-21 21:57:39 UTC Link ID OpenStack gerrit 846531
Steve Baker 2022-06-26 23:36:05 UTC Status ON_DEV MODIFIED
Fixed In Version python-metalsmith-1.4.3-0.20220626221811.324b758.el8ost
Jon Schlueter 2022-06-28 11:55:53 UTC Fixed In Version python-metalsmith-1.4.3-0.20220626221811.324b758.el8ost python-metalsmith-1.4.3-0.20220626220340.324b758.el9osttrunk
CC jschluet
Jon Schlueter 2022-06-30 20:37:24 UTC Fixed In Version python-metalsmith-1.4.3-0.20220626220340.324b758.el9osttrunk python-metalsmith-1.4.3-0.20220626220340.324b758.el9ost
Jon Schlueter 2022-07-01 14:20:45 UTC Status MODIFIED ON_QA
Rabi Mishra 2022-07-07 03:38:35 UTC CC ramishra
David Rosenfeld 2022-07-07 12:55:12 UTC Status ON_QA ON_DEV
Steve Baker 2022-07-07 23:34:22 UTC Link ID OpenStack gerrit 849052
Steve Baker 2022-07-13 01:12:47 UTC Fixed In Version python-metalsmith-1.4.3-0.20220626220340.324b758.el9ost python-metalsmith-1.4.3-0.20220712230441.324b758.el9ost
Status ON_DEV MODIFIED
Jon Schlueter 2022-07-15 20:39:57 UTC Fixed In Version python-metalsmith-1.4.3-0.20220712230441.324b758.el9ost python-metalsmith-1.4.3-0.20220712230441.324b758.el9osttrunk
OSP Team 2022-07-18 06:07:48 UTC Fixed In Version python-metalsmith-1.4.3-0.20220712230441.324b758.el9osttrunk python-metalsmith-1.4.3-0.20220712230441.324b758.el9ost
Jon Schlueter 2022-07-18 18:59:55 UTC Status MODIFIED ON_QA
Jason Paroly 2022-07-25 13:54:31 UTC QA Contact drosenfe
CC jparoly
Rabi Mishra 2022-07-26 01:54:34 UTC Status ON_QA ON_DEV
Link ID OpenStack gerrit 850829
Steve Baker 2022-07-26 21:21:31 UTC Fixed In Version python-metalsmith-1.4.3-0.20220712230441.324b758.el9ost
Link ID OpenStack gerrit 850919
Steve Baker 2022-07-26 21:29:46 UTC Status ON_DEV POST
Rabi Mishra 2022-07-27 01:43:30 UTC Status POST MODIFIED
Fixed In Version tripleo-ansible-3.3.1-0.20220727011846.fa5422f.el8osttrunk
OSP Team 2022-07-27 06:02:15 UTC Fixed In Version tripleo-ansible-3.3.1-0.20220727011846.fa5422f.el8osttrunk tripleo-ansible-3.3.1-0.20220727011846.fa5422f.el8ost
Rabi Mishra 2022-07-27 08:05:11 UTC Fixed In Version tripleo-ansible-3.3.1-0.20220727011846.fa5422f.el8ost tripleo-ansible-3.3.1-0.20220727020907.fa5422f.el9ost
errata-xmlrpc 2022-07-28 17:56:10 UTC Status MODIFIED ON_QA
Jon Schlueter 2022-08-02 11:29:19 UTC Fixed In Version tripleo-ansible-3.3.1-0.20220727020907.fa5422f.el9ost python-metalsmith-1.4.3-0.20220712230441.324b758.el9ost tripleo-ansible-3.3.1-0.20220727020907.fa5422f.el9ost
Component python-metalsmith tripleo-ansible
Cédric Jeanneret 2022-08-17 11:55:02 UTC CC cjeanner
Status ON_QA POST
Cédric Jeanneret 2022-08-17 11:57:45 UTC Target Milestone beta z1
Steve Baker 2022-11-01 01:26:28 UTC Target Milestone z1 ---
Fixed In Version python-metalsmith-1.4.3-0.20220712230441.324b758.el9ost tripleo-ansible-3.3.1-0.20220727020907.fa5422f.el9ost python-metalsmith-1.4.3-0.20220712230441.324b758.el9ost tripleo-ansible-3.3.1-1.20220729002029.f02886a.el9ost
Status POST MODIFIED
Target Release 17.0 ---
errata-xmlrpc 2022-11-29 14:53:56 UTC Status MODIFIED ON_QA
Andy Stillman 2023-05-26 12:37:59 UTC Flags needinfo?(sbaker)
Steve Baker 2023-05-28 21:06:07 UTC Doc Text Cause:
Metalsmith lookup by name attempts the allocation name before the node name

Consequence:
In environments where the node naming scheme overlaps with the overcloud role naming scheme, the wrong node may be unprovsioned during undeploy

Fix:
Nodes for unprovision are now referenced by allocation name (hostname), only falling back to node name if the hostname doesn't exist.

Result: The correct node is always unprovisioned.
Doc Type If docs needed, set a value Bug Fix
Flags needinfo?(sbaker)
Irina 2023-06-07 09:59:12 UTC CC igallagh
Doc Text Cause:
Metalsmith lookup by name attempts the allocation name before the node name

Consequence:
In environments where the node naming scheme overlaps with the overcloud role naming scheme, the wrong node may be unprovsioned during undeploy

Fix:
Nodes for unprovision are now referenced by allocation name (hostname), only falling back to node name if the hostname doesn't exist.

Result: The correct node is always unprovisioned.
Before this update, after deleting a bare-metal overcloud node the node was still being listed as active by the `metalsmith` tool. This happened in environments where the node naming scheme overlapped with the overcloud role naming scheme, which could result in the wrong node being unprovisioned during undeploy. Because the `metalsmith` tool uses the allocation name (hostname) first to lookup the status of bare-metal nodes, it was sometimes finding deleted nodes as still active.
+
With this update, nodes to be unprovisioned are now referenced by allocation name (hostname), which ensures that the correct node is always unprovisioned. The nodes are only referenced by node name if the hostname doesn't exist.
Flags needinfo?(sbaker)
Steve Baker 2023-06-09 02:33:58 UTC Flags needinfo?(sbaker)
Evelina Shames 2023-07-18 13:22:51 UTC CC eshames
QA Contact drosenfe jlabarre
David Rosenfeld 2023-07-18 13:42:31 UTC Status ON_QA VERIFIED
James Smith 2023-08-13 20:28:15 UTC CC jamsmith
Doc Text Before this update, after deleting a bare-metal overcloud node the node was still being listed as active by the `metalsmith` tool. This happened in environments where the node naming scheme overlapped with the overcloud role naming scheme, which could result in the wrong node being unprovisioned during undeploy. Because the `metalsmith` tool uses the allocation name (hostname) first to lookup the status of bare-metal nodes, it was sometimes finding deleted nodes as still active.
+
With this update, nodes to be unprovisioned are now referenced by allocation name (hostname), which ensures that the correct node is always unprovisioned. The nodes are only referenced by node name if the hostname doesn't exist.
Before this update, a bare-metal overcloud node the node was listed as active by the `metalsmith` tool even after being deleted. This happened in environments where the node naming scheme overlapped with the overcloud role naming scheme, which could result in the wrong node being unprovisioned during undeploy. Because the `metalsmith` tool uses the allocation name (hostname) first to lookup the status of bare-metal nodes, it was sometimes finding deleted nodes as still active.
+
With this update, nodes to be unprovisioned are now referenced by allocation name (hostname), which ensures that the correct node is always unprovisioned. The nodes are only referenced by node name if the hostname doesn't exist.
Irina 2023-08-14 08:26:12 UTC Doc Text Before this update, a bare-metal overcloud node the node was listed as active by the `metalsmith` tool even after being deleted. This happened in environments where the node naming scheme overlapped with the overcloud role naming scheme, which could result in the wrong node being unprovisioned during undeploy. Because the `metalsmith` tool uses the allocation name (hostname) first to lookup the status of bare-metal nodes, it was sometimes finding deleted nodes as still active.
+
With this update, nodes to be unprovisioned are now referenced by allocation name (hostname), which ensures that the correct node is always unprovisioned. The nodes are only referenced by node name if the hostname doesn't exist.
Before this update, a bare-metal overcloud node was listed as active by the `metalsmith` tool even after being deleted. This happened in environments where the node naming scheme overlapped with the overcloud role naming scheme, which could result in the wrong node being unprovisioned during undeploy. Because the `metalsmith` tool uses the allocation name (hostname) first to lookup the status of bare-metal nodes, it was sometimes finding deleted nodes as still active.
+
With this update, nodes to be unprovisioned are now referenced by allocation name (hostname), which ensures that the correct node is always unprovisioned. The nodes are only referenced by node name if the hostname doesn't exist.
errata-xmlrpc 2023-08-16 00:02:47 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-08-16 01:11:11 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2023-08-16 01:11:11 UTC
errata-xmlrpc 2023-08-16 01:11:51 UTC Link ID Red Hat Product Errata RHEA-2023:4577

Back to bug 2092444