Bug 2007268 - power_sync failed ironic conductor when using ipmi driver
Summary: power_sync failed ironic conductor when using ipmi driver
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: z1
: 16.2 (Train on RHEL 8.4)
Assignee: Julia Kreger
QA Contact:
URL:
Whiteboard:
: 2006603 2011422 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-23 12:53 UTC by Uemit Seren
Modified: 2022-01-21 09:57 UTC (History)
10 users (show)

Fixed In Version: openstack-ironic-13.0.8-2.20210528130909.el8ost.1
Doc Type: Bug Fix
Doc Text:
Before this update, a lock handling issue prevented IPMI-based nodes from recording the hardware vendor as part of power state synchronization. This issue caused the power state synchronization to fail, and nodes that used the `ipmi` hardware type entered the `Maintenance` state. With this update, the lock is handled correctly and the power state synchronization for bare metal nodes that use the `ipmi` hardware type work correctly and no locking errors occur.
Clone Of:
Environment:
Last Closed: 2021-12-09 20:41:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 810656 0 None stable/ussuri: MERGED ironic: [Stable only] remove require_exclusive_lock from detect_vendor (I051da583ef6e5131ce36b70b862e91cfdae2b213) 2021-10-25 13:44:58 UTC
Red Hat Issue Tracker OSP-9853 0 None None None 2021-11-17 09:54:29 UTC
Red Hat Knowledge Base (Solution) 6395301 0 None None None 2021-10-09 08:48:31 UTC
Red Hat Product Errata RHBA-2021:5067 0 None None None 2021-12-09 20:41:46 UTC

Description Uemit Seren 2021-09-23 12:53:32 UTC
Description of problem:

The power_sync for baremetal nodes that use the ipmi driver fails with following error messages and the node is put into maintenance mode:

2021-09-23 13:42:33.514 7 ERROR ironic.conductor.manager [req-06c1ac49-2619-429f-9d3d-c96953a37def - - - - -] During sync_power_state, max retries exceeded for node 5a770848-5ee9-4b96-8560-d0434088779a, node state None does not match expected state 'None'. Updating DB state to 'None' Switching node to maintenance mode. Error: An exclusive lock is required, but the current context has a shared lock.: ironic.common.exception.ExclusiveLockRequired: An exclusive lock is required, but the current context has a shared lock.

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


How reproducible:

always

Steps to Reproduce:
1. Enroll & manage a node
2. Wait until node is put into maintenance mode

Actual results:

Node power state is "None" and node is put into maintenance state

Expected results:

Node power state should be "Power off" and node should not be in maintenance state

Additional info:

Current workaround is to set vendor=ignoreme:
openstack baremetal node set <node>--property vendor=ignoreme

According to upstream developers following patch needs to be backported to Train release: 
https://review.opendev.org/c/openstack/ironic/+/810656

Comment 5 Steve Baker 2021-09-28 19:40:41 UTC
*** Bug 2006603 has been marked as a duplicate of this bug. ***

Comment 6 Steve Baker 2021-10-12 20:02:59 UTC
*** Bug 2011422 has been marked as a duplicate of this bug. ***

Comment 27 errata-xmlrpc 2021-12-09 20:41:22 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 16.2.1 (Train)), 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/RHBA-2021:5067


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