Bug 1559351

Summary: [RFE] Automatic recovery from power faults
Product: Red Hat OpenStack Reporter: Dmitry Tantsur <dtantsur>
Component: openstack-ironicAssignee: Dmitry Tantsur <dtantsur>
Status: CLOSED ERRATA QA Contact: mlammon
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: bfournie, dsneddon, mburns, racedoro, rhel-osp-director-maint, srevivo
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://specs.openstack.org/openstack/ironic-specs/specs/approved/power-fault-recovery.html
Whiteboard:
Fixed In Version: openstack-ironic-11.0.1-0.20180710182436.d29dab2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:49:11 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:
Bug Depends On:    
Bug Blocks: 1614489, 1636972    

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