Bug 1559351 - [RFE] Automatic recovery from power faults
Summary: [RFE] Automatic recovery from power faults
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M2
: 14.0 (Rocky)
Assignee: Dmitry Tantsur
QA Contact: mlammon
URL: http://specs.openstack.org/openstack/...
Whiteboard:
Depends On:
Blocks: 1614489 1636972
TreeView+ depends on / blocked
 
Reported: 2018-03-22 11:19 UTC by Dmitry Tantsur
Modified: 2019-01-11 11:49 UTC (History)
6 users (show)

Fixed In Version: openstack-ironic-11.0.1-0.20180710182436.d29dab2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:49:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 556758 0 None MERGED Power fault recovery: apply fault 2020-03-19 19:26:27 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:49:30 UTC

Description Dmitry Tantsur 2018-03-22 11:19:24 UTC 
Currently if a node gets into maintenance due to a power problem or BMC unavailability, it never comes back without operator's intervention. We would like to enable ironic to check BMC accessibility from time to time, and to return nodes back into operation.
Comment 1 Dmitry Tantsur 2018-03-22 11:20:38 UTC 
Proposing for Rocky. There is an interest upstream to finish this. Will be a huge usability improvement for both under- and overcloud.
Comment 4 Dmitry Tantsur 2018-05-30 11:57:11 UTC 
The core of this feature has landed. While there are useful API additions to follow, the landed code matches the description of the RFE, so moving to POST.
Comment 7 errata-xmlrpc 2019-01-11 11:49:11 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, 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-2019:0045
Note You need to log in before you can comment on or make changes to this bug.