Bug 2009850

Summary:	Power off fails for drivers that don't support Soft power off
Product:	OpenShift Container Platform	Reporter:	Zane Bitter <zbitter>
Component:	Bare Metal Hardware Provisioning	Assignee:	Zane Bitter <zbitter>
Bare Metal Hardware Provisioning sub component:	baremetal-operator	QA Contact:	Amit Ugol <augol>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	augol, fj-lsoft-rh-cnt, hyasuhar, lshilin
Version:	4.9	Keywords:	OtherQA, Triaged
Target Milestone:	---
Target Release:	4.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2006101	Environment:
Last Closed:	2021-11-10 21:02:21 UTC	Type:	---
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:	2006101
Bug Blocks:

Description Zane Bitter 2021-10-01 19:03:34 UTC

+++ This bug was initially created as a clone of Bug #2006101 +++

When an ironic driver doesn't support soft power off, we are supposed to fall back to doing a hard power off. This was inadvertently broken in OpenShift 4.9. Now when the driver doesn't support soft power off we end up returning a 'transient' error and retrying in an infinite loop.

The Fujitsu driver is known to not support soft power off when its agent is not available on the host.

Comment 2 Dmitry Tantsur 2021-10-15 10:02:00 UTC

The actual PR is https://github.com/openshift/baremetal-operator/pull/184

Comment 7 Fujitsu container team 2021-11-05 07:32:55 UTC

Hi Zane,

Fujitsu verified that soft shutdown feature worked correctly with OCP4.9.6 which includes PR184.

Best Regards,
Yasuhiro Futakawa

Comment 8 Amit Ugol 2021-11-05 15:27:05 UTC

Many thanks for that.
Based on Fujitsu's success to validate the fix, I am closing it as OtherQA.

Comment 10 errata-xmlrpc 2021-11-10 21:02:21 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 (OpenShift Container Platform 4.9.6 bug fix update), 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:4119