Bug 1267190
| Summary: | Rear creates bootable ISO file only for x86_64, ppc64 and ppc64le architectures | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Tereza Cerna <tcerna> | |
| Component: | rear | Assignee: | Pavel Cahyna <pcahyna> | |
| Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 7.3 | CC: | dhorak, pcahyna, tbowling, yselkowi | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1267469 1672334 (view as bug list) | Environment: | ||
| Last Closed: | 2020-12-15 07:37:05 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: | 1455939 | |||
| Bug Blocks: | 1400961, 1472751, 1481451 | |||
|
Comment 4
Petr Hracek
2015-09-30 06:51:50 UTC
Patch for PPC64LE already exists in upstream. See https://github.com/rear/rear/pull/665 https://github.com/rear/rear/pull/663 https://github.com/mmitsugi/rear/commit/bf705a445172aa2d1bf13b1e97ddcb1c0f529152 This bug is valid only for s390x. The rest architectures are ok. This is the same bug as for RHEL-6.8: https://bugzilla.redhat.com/show_bug.cgi?id=1309597 So... Small change: x86_64, ppc64, ppc64le - OK s390x, aarch64 - FAIL - don't create ISO file # rear -v mkbackup Relax-and-Recover 1.17.2 / Git Using log file: /var/log/rear/rear-ibm-z10-73.log Creating disk layout Creating root filesystem layout Copying files and directories Copying binaries and libraries Copying kernel modules Creating initramfs # echo $? 0 # After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |