Bug 2216434
| Summary: | pcs: Will start to FTBFS after bug 2166383 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Florian Weimer <fweimer> |
| Component: | pcs | Assignee: | Michal Pospisil <mpospisi> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 9.3 | CC: | cluster-maint, idevat, mjw, mlisik, mmazoure, mpospisi, nhostako, omular, tojeline |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 9.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pcs-0.11.6-2.el9 | Doc Type: | No Doc Update |
| Doc Text: |
This has no effect on the resulting rpm package (other than the fact it's actually possible to build it).
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-07 08:23:11 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: | |||
| Bug Blocks: | 2166383 | ||
|
Description
Florian Weimer
2023-06-21 10:46:51 UTC
We are aware of this issue because we already saw it in Fedora. However, we thought that this change would only appear in RHEL10. The plan is to BuildRequire the debugedit package and invoke the find-debuginfo script from %{_bindir}/find-debuginfo (or just by calling find-debuginfo).
DebugInfo generation is not broken. We do not have a DebugInfo package since pcs is written in Python/Ruby. However, we bundle some rubygems that have C extensions for which we generate MiniDebugInfo with find-debuginfo.sh. The fix in Fedora for this issue was to replace (and stop bundling) the last unpackaged rubygems. Calling the find-debuginfo script is not necessary in Fedora anymore. That is not the situation in RHEL because no rubygems that we use are packaged there. We still need to call find-debuginfo to generate MiniDebugInfo for those C extensions of our bundled rubygems.
Since we do not plan on making another package for RHEL 9.3 and this is a build-time issue, this will be fixed in 9.4. But if we have to do another build for 9.3, the fix will be included there of course.
Call to `/usr/lib/rpm/find-debuginfo.sh` was changed to `find-debuginfo` along with adding `BuildRequires: debugedit`. Mock build and scratch build both pass with find-debuginfo from debugedit. From the build.log: BEFORE: + /usr/lib/rpm/find-debuginfo.sh -j2 -m -i -S debugsourcefiles.list extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-1.el9.x86_64/usr/lib64/pcs/pcs_bundled/packages/tornado/speedups.abi3.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-1.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/ffi-1.15.5/ffi_c.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-1.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/nio4r-2.5.9/nio4r_ext.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-1.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/puma-6.3.0/puma/puma_http11.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-1.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/ffi-1.15.5/ext/ffi_c/ffi_c.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-1.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/nio4r-2.5.9/ext/nio4r/nio4r_ext.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-1.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/puma-6.3.0/ext/puma_http11/puma_http11.so AFTER: + find-debuginfo -j2 -m -i -S debugsourcefiles.list extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcs/pcs_bundled/packages/tornado/speedups.abi3.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/ffi-1.15.5/ffi_c.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/nio4r-2.5.9/nio4r_ext.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/puma-6.3.0/puma/puma_http11.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/ffi-1.15.5/ext/ffi_c/ffi_c.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/nio4r-2.5.9/ext/nio4r/nio4r_ext.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/puma-6.3.0/ext/puma_http11/puma_http11.so DevTestResults: The build passed: https://kojihub.stream.centos.org/koji/taskinfo?taskID=2481924. From the build.log: + find-debuginfo -j2 -m -i -S debugsourcefiles.list extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcs/pcs_bundled/packages/tornado/speedups.abi3.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/ffi-1.15.5/ffi_c.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/nio4r-2.5.9/nio4r_ext.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/extensions/x86_64-linux/3.0.0/puma-6.3.0/puma/puma_http11.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/ffi-1.15.5/ext/ffi_c/ffi_c.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/nio4r-2.5.9/ext/nio4r/nio4r_ext.so extracting debug info from /builddir/build/BUILDROOT/pcs-0.11.6-2.el9.x86_64/usr/lib64/pcsd/vendor/bundle/gems/puma-6.3.0/ext/puma_http11/puma_http11.so (In reply to Michal Pospisil from comment #3) > Call to `/usr/lib/rpm/find-debuginfo.sh` was changed to `find-debuginfo` > along with adding `BuildRequires: debugedit`. Mock build and scratch build > both pass with find-debuginfo from debugedit. For verification purposes, this is the aforementioned fix that can be spotted in pcs.spec upon extracting the pcs srpm: https://gitlab.com/redhat/centos-stream/rpms/pcs/-/commit/a8b1b4c1d87e71cfaed3b04075b503678f67f548#40a712d386be33f54f38783a3533ad4fb9bfdfa9_386_392 This bz is just for build purposes, only sanity check will be done, together with a run of regression tests.
AFTER:
======
## pcs version pcs-0.11.6-3.el9
[root@virt-537 srcrpm]# rpm2cpio pcs-0.11.6-3.el9.src.rpm | cpio -civ '*.spec'
pcs.spec
93106 blocks
[root@virt-537 srcrpm]# cat pcs.spec | grep "find-debuginfo -j2 -m -i -S debugsourcefiles.list"
find-debuginfo -j2 -m -i -S debugsourcefiles.list
[root@virt-537 srcrpm]# echo $?
0
> OK: The fix mentioned in comment 6 is present in the package.
Marking as VERIFIED SanityOnly for pcs-0.11.6-3.el9.
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 (Low: pcs security, 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/RHSA-2023:6316 |