Bug 1983003
| Summary: | PPC64le: grub2-install doesn't execute properly, making the recovered system unbootable | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> |
| Component: | rear | Assignee: | Pavel Cahyna <pcahyna> |
| Status: | CLOSED ERRATA | QA Contact: | David Jež <djez> |
| Severity: | high | Docs Contact: | Prerana Sharma <presharm> |
| Priority: | high | ||
| Version: | 8.4 | CC: | djez, lzaoral, ovasik, pcahyna, presharm |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | ppc64le | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rear-2.6-1.el8 | Doc Type: | Bug Fix |
| Doc Text: |
.BM Power Systems, Little Endian architecture machines with multipath can now be safely recovered using ReaR
Previously, the `/sys` file system was not mounted in the chroot when ReaR was recovering the system. The `ofpathname` executable on the IBM Power Systems, Little Endian architecture failed when installing the boot loader. Consequently, the error remained undetected and the recovered system was unbootable.
With this update, ReaR now mounts the `/sys` file system in the recovery chroot. ReaR ensures that `ofpathname` is present in the rescue system on Power Systems, Little Endian architecture machines.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-09 18:53:41 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: | 1988493 | ||
| Bug Blocks: | |||
|
Description
Renaud Métrich
2021-07-16 08:54:30 UTC
I tried to reproduce the problem on RHEL 8.4. While I can see the errors from ofpathname in the log, the recovered system boots just fine. Is the error really so fatal for grub2-install? 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 (rear bug fix and enhancement 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/RHEA-2021:4344 |