Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 423010[details]
save/restore ld.so.cache in mkdumprd
+++ This bug was initially created as a clone of Bug #589768 +++
Created an attachment (id=412159)
save/restore ld.so.cache in mkdumprd
Description of problem:
When mkdumprd is run there's an ldconfig -l call to run ldd with a different cache, and then another ldconfig call follows to re-generate the cache. This can present problems when mkdumprd is run during boot. The kdump service (S20) is started before autofs (S28), so when ldconfig is run it will remove any symlinks to shared libs which reside on autofs managed filesystems.
To resolve this we should instead save/restore the original ld.so.cache. This way we ensure we end up getting back to the original cache even if network filesystems aren't yet available to us.
Version-Release number of selected component (if applicable):
kexec-tools-1.102pre-96.el5
How reproducible:
100%
Steps to Reproduce:
1. install shared libs on fs managed by autofs
2. touch /etc/kdump.conf
3. reboot
Actual results:
symlinks to shared libs on autofs managed fs's are gone
Expected results:
symlinks are preserved
Additional info:
Comment 1RHEL Program Management
2010-06-10 18:43:22 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
reason for 6.0 exception request is that bug 589768 is slated to be fixed in 5.6 and thus once 5.6 is released this will become a regression, thus trying to prevent that.
Dave, in case we have a read-only root filesystem, I switched to 'ldconfig -N'. Just fyi.
Comment 9releng-rhel@redhat.com
2010-11-11 14:46:10 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.