Bug 1991657

Summary:	ironic-inspector not retrying when Ironic nodes are locked
Product:	Red Hat OpenStack	Reporter:	Julia Kreger <jkreger>
Component:	openstack-ironic-inspector	Assignee:	Julia Kreger <jkreger>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	17.0 (Wallaby)	CC:	jamsmith, jparoly, pgrist, rheslop, sbaker
Target Milestone:	beta	Keywords:	Triaged
Target Release:	17.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ironic-inspector-10.6.2-0.20220118051837.8f97076.el8ost	Doc Type:	Bug Fix
Doc Text:	Before this update, baremetal node introspection failed with an error and did not retry, when the node had a transient lock on it. + With this update, you can perform introspection even when the node has a lock.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-21 12:16:15 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 Julia Kreger 2021-08-09 15:44:35 UTC

Description of problem:

Ironic-inspector does not retry when a node has a transient lock on it. This was a silent feature of python-ironicclient, however ironic-inspector was moved to use openstacksdk during the ussuri development cycle.

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

This issue started in ironic-inspector 10.1.0, and is present in OSP 17, at present.

How reproducible:

Very sporadically, however failures will halt the TripleO inspection process.

Steps to Reproduce:
1. Enroll/Manage a node in ironic
2. Inspect the node
3. Node should be introspected and introspection should complete successfully.

Actual results:

Node introspection fails with an error.

Expected results:

Introspection passes


Additional info:

None, see storyboard link attached.

Comment 1 Steve Baker 2021-08-17 19:34:48 UTC

Wallaby fix has landed

Comment 11 errata-xmlrpc 2022-09-21 12:16:15 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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543