Bug 2229862
| Summary: | broken link and library | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | tbsky <tbskyd> |
| Component: | rear | Assignee: | Pavel Cahyna <pcahyna> |
| Status: | ASSIGNED --- | QA Contact: | CS System Management SST QE <rhel-cs-system-management-subsystem-qe> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.2 | CC: | pcahyna |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
Hi: I upgrade some machines from RHEL 9.1 to 9.2. and "rear mkrecue" shows below: Broken symlink '/etc/pki/tls/fips_local.cnf' in recovery system because 'readlink' cannot determine its link target Broken symlink '/usr/lib/firmware/qcom/LENOVO/21BX.xz' in recovery system because 'readlink' cannot determine its link target There are binaries or libraries in the ReaR recovery system that need additional libraries /usr/lib64/systemd/libsystemd-core-252.so requires additional libraries libsystemd-shared-252.so => not found "/usr/lib/firmware" always has broken links. although it maybe fixed in some versions (which are rare, firmware packager didn't care about broken). so maybe we should skip "usr/lib/firmware" like skipping broken kernel links under "/usr/lib/modules". the openssl broken link is new at RHEL 9.2 as below, I don't know what is it: >ls -la /etc/pki/tls/fips_local.cnf lrwxrwxrwx 1 root root 50 Jul 13 17:37 /etc/pki/tls/fips_local.cnf -> /etc/crypto-policies/back-ends/openssl_fips.config the systemd broken library is also new at RHEL 9.2. I saw debian/Ubuntu also has similar problem at upstream report, only SuSe is fine. https://github.com/rear/rear/issues/3021 >ldd /usr/lib64/systemd/libsystemd-core-252.so linux-vdso.so.1 (0x00007ffee53d6000) libsystemd-shared-252.so => not found libseccomp.so.2 => /lib64/libseccomp.so.2 (0x00007f55c29e0000) libpam.so.0 => /lib64/libpam.so.0 (0x00007f55c29ce000) libaudit.so.1 => /lib64/libaudit.so.1 (0x00007f55c29a0000) libkmod.so.2 => /lib64/libkmod.so.2 (0x00007f55c2985000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f55c2958000) libmount.so.1 => /lib64/libmount.so.1 (0x00007f55c2913000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f55c28f8000) libc.so.6 => /lib64/libc.so.6 (0x00007f55c2600000) libeconf.so.0 => /lib64/libeconf.so.0 (0x00007f55c28ed000) libm.so.6 => /lib64/libm.so.6 (0x00007f55c2812000) libcap-ng.so.0 => /lib64/libcap-ng.so.0 (0x00007f55c2c0e000) libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f55c2529000) liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f55c24fd000) libz.so.1 => /lib64/libz.so.1 (0x00007f55c24e3000) libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007f55c2000000) libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007f55c2447000) /lib64/ld-linux-x86-64.so.2 (0x00007f55c2c20000) libblkid.so.1 => /lib64/libblkid.so.1 (0x00007f55c1fc8000) >ls -la /usr/lib64/systemd/ total 5752 drwxr-xr-x 2 root root 68 Aug 7 12:58 . dr-xr-xr-x 63 root root 53248 Aug 7 13:00 .. -rwxr-xr-x 1 root root 2174032 Jul 17 16:34 libsystemd-core-252.so -rwxr-xr-x 1 root root 3640160 Jul 17 16:34 libsystemd-shared-252.so