This is a public version of https://bugzilla.redhat.com/show_bug.cgi?id=2005163 to meet github automation requirements.
*** Bug 2005163 has been marked as a duplicate of this bug. ***
*** Bug 2005165 has been marked as a duplicate of this bug. ***
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!
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
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
(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.
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