Bug 1991657 - ironic-inspector not retrying when Ironic nodes are locked
Summary: ironic-inspector not retrying when Ironic nodes are locked
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic-inspector
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 17.0
Assignee: Julia Kreger
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-09 15:44 UTC by Julia Kreger
Modified: 2022-09-21 21:38 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2022-09-21 12:16:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack Storyboard 2009107 0 None None None 2021-08-09 15:44:34 UTC
OpenStack gerrit 803935 0 None None None 2021-08-09 15:44:34 UTC
OpenStack gerrit 804167 0 None None None 2021-09-01 17:40:53 UTC
Red Hat Issue Tracker OSP-6927 0 None None None 2021-11-15 12:59:04 UTC
Red Hat Product Errata RHEA-2022:6543 0 None None None 2022-09-21 12:16:56 UTC

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
Note You need to log in before you can comment on or make changes to this bug.