Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2011753

Summary: Ironic resumes clean before raid configuration job is actually completed
Product: OpenShift Container Platform Reporter: Jacob Anders <janders>
Component: Bare Metal Hardware ProvisioningAssignee: Jacob Anders <janders>
Bare Metal Hardware Provisioning sub component: ironic QA Contact: Amit Ugol <augol>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: fj-lsoft-rh-cnt, hase.jin, hfukumot, jniu, rpittau, tsedovic
Version: 4.10Keywords: OtherQA, Triaged
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2012798 (view as bug list) Environment:
Last Closed: 2022-03-10 16:17:59 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: 1920358, 2012798    

Comment 1 Jacob Anders 2021-10-07 09:52:21 UTC
This is a public version of https://bugzilla.redhat.com/show_bug.cgi?id=2005163 to meet github automation requirements.

Comment 2 Jacob Anders 2021-10-07 23:52:33 UTC
*** Bug 2005163 has been marked as a duplicate of this bug. ***

Comment 3 Jacob Anders 2021-10-07 23:54:54 UTC
*** Bug 2005165 has been marked as a duplicate of this bug. ***

Comment 7 Jacob Anders 2021-10-10 22:41:19 UTC
Please note this will need to be verified with OtherQA as I do not believe we have iRMC-enabled hardware available in the lab.

Hase-san, would your team be able to verify this fix?

https://amd64.ocp.releases.ci.openshift.org/releasestream/4.10.0-0.nightly/release/4.10.0-0.nightly-2021-10-10-083341 should be an accepted build which includes the fix.

We'll need to have this verified in order to be able to proceed with the 4.9 backports.

Thank you!

Comment 8 Fujitsu container team 2021-10-11 01:52:31 UTC
Hi Jacob,

>Hase-san, would your team be able to verify this fix?
Yes, Fujitsu is going to verify this fix with the OCP4.10 latest nightly.

Best Regards,
Yasuhiro Futakawa

Comment 9 Fujitsu container team 2021-10-11 09:13:29 UTC
Hi Jacob,

Fujitsu confirmed that the fixes has been merged in nightly 4.10.0-0.nightly-2021-10-10-051521.
And we verified this version of nightly, and we confirmed that the problem was resolved.

Best Regards,
Yasuhiro Futakawa

Comment 10 Jacob Anders 2021-10-11 09:41:09 UTC
(In reply to Fujitsu container team from comment #9)
> Hi Jacob,
> 
> Fujitsu confirmed that the fixes has been merged in nightly
> 4.10.0-0.nightly-2021-10-10-051521.
> And we verified this version of nightly, and we confirmed that the problem
> was resolved.
> 
> Best Regards,
> Yasuhiro Futakawa

Thank you Yasuhiro and Fujitsu Team.

Marking this BZ as VERIFIED/OtherQA.

Comment 13 errata-xmlrpc 2022-03-10 16:17:59 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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056