Bug 2088319
| Summary: | Redfish set boot device failed for node in OCP 4.9 latest RC | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jacob Anders <janders> |
| Component: | Bare Metal Hardware Provisioning | Assignee: | Jacob Anders <janders> |
| Bare Metal Hardware Provisioning sub component: | ironic | QA Contact: | Amit Ugol <augol> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | augol, dtantsur, imelofer, manrodri, rpittau, tsedovic |
| Version: | 4.9 | Keywords: | OtherQA |
| Target Milestone: | --- | ||
| Target Release: | 4.9.z | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Release Note | |
| Doc Text: |
Since adding eTag handling in Ironic (this was implemented during upstream Yoga cycle - patches: https://review.opendev.org/c/openstack/sushy/+/818114 and https://review.opendev.org/c/openstack/sushy/+/818110 ) issues with eTag handling on old firmware versions were increasingly observed, in particular on HP Machines. For example on DL360G10, iLo 5 2.63 or later is required otherwise issues with eTag handling in firmware may prevent Ironic from successfully provisioning the server. It is always recommended to run latest firmware, however in case of eTag issues it is mandatory to upgrade to latest firmware prior to taking any further troubleshooting steps.
|
Story Points: | --- |
| Clone Of: | 2088196 | Environment: | |
| Last Closed: | 2022-05-25 04:30:33 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: | 2088716 | ||
| Bug Blocks: | 2088196 | ||
|
Comment 1
Jacob Anders
2022-05-19 13:01:33 UTC
Note: we verified that the proposed fix works in https://bugzilla.redhat.com/show_bug.cgi?id=2088196#c7. I will now work through the OCP backport process to ensure prerequisites are met in order to be able to merge the fix across the affected releases (noop BZ for 4.10/4.11 may be required to meet process requirements). Adding pending sushy release (which is a prerequisite for raising OCP PR) for tracking, currently under review. Current status: we have a tested fix merged upstream ( see https://bugzilla.redhat.com/show_bug.cgi?id=2088196#c7 ). We are waiting for the release of the library with the fix so that we can raise a downstream PR to include the fix in the Ironic image corresponding to this OCP version. OCP 4.9 PR is now raised. This has been fixed by https://review.opendev.org/c/openstack/sushy/+/842461/. I have performed verification on 4.8 with Manuel by manually patching 4.8.40 container with this fix. The fix is 100% identical on 4.8 and 4.9 and it's an automatic cherry-pick hence this is sufficient information to successfully verify this fix (4.9) as well. Setting status to VERIFIED/OtherQA. ( forgot the link to 4.8 BZ with the confirmation that verification has been successful - it's here: https://bugzilla.redhat.com/show_bug.cgi?id=2088196#c11) 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.9.35 bug fix and 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:2283 |