Bug 662530
Summary: | ln: creating symbolic link `/tmp/initrd.ta4308/lib/libc.so.6' to `/lib/power6/libc.so.6': File exists | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Chao Ye <cye> |
Component: | kexec-tools | Assignee: | Cong Wang <amwang> |
Status: | CLOSED ERRATA | QA Contact: | WANG Chao <chaowang> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.6 | CC: | ccui, cye, czhang, phan, rkhan, ruyang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ppc64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kexec-tools-1_102pre-134_el5 | Doc Type: | Bug Fix |
Doc Text: |
No description necessary
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-02-21 03:17:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chao Ye
2010-12-13 02:14:17 UTC
Reproduced with 5.7 internal alpha. Reproduced with RHEL5-Server-U7. Reproduce with kexec-tools-1.102pre-126.el5_6.6: # /etc/init.d/kdump restart Stopping kdump:[ OK ] Detected change(s) the following file(s): /etc/kdump.conf Rebuilding /boot/initrd-2.6.18-274.el5kdump.img ln: creating symbolic link `/tmp/initrd.Vg4955/lib/libc.so.6' to `/lib/power6x/libc.so.6': File exists ln: creating symbolic link `/tmp/initrd.Vg4955/lib/libc.so.6' to `/lib/power6/libc.so.6': File exists Verified with kexec-tools-1.102pre-134.el5 Stopping kdump:[ OK ] Detected change(s) the following file(s): /etc/kdump.conf Rebuilding /boot/initrd-2.6.18-274.el5kdump.img Starting kdump:[ OK ] Change bug status to verified Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary 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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0152.html |