Bug 1812434 - [Fedora] kdump-capture.service: 'ln: failed to create symbolic link'
Summary: [Fedora] kdump-capture.service: 'ln: failed to create symbolic link'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kexec-tools
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kairui Song
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1812393 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-11 10:52 UTC by Bhupesh Sharma
Modified: 2020-04-08 05:06 UTC (History)
6 users (show)

Fixed In Version: kexec-tools-2.0.20-11.fc32 kexec-tools-2.0.20-11.fc31
Clone Of:
Environment:
Last Closed: 2020-04-01 00:17:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bhupesh Sharma 2020-03-11 10:52:42 UTC
Description of problem:

Running kdumpctl restart on latest Fedora leading to the following failure message:

[root@hpe-apollo-cn99xx-14-vm-03 ~]# kdumpctl restart
kexec: unloaded kdump kernel
Stopping kdump: [OK]
No kdump initial ramdisk found.
Rebuilding /boot/initramfs-5.6.0-0.rc5.git0.1.fc33.aarch64kdump.img
ln: failed to create symbolic link '/var/tmp/dracut.a9NXzb/initramfs//usr/lib/systemd/system/initrd.target.wants/kdump-capture.service': No such file or directory
kexec: loaded kdump kernel
Starting kdump: [OK]

Version-Release number of selected component (if applicable):

[root@hpe-apollo-cn99xx-14-vm-03 ~]# uname -rn
hpe-apollo-cn99xx-14-vm-03.khw4.lab.eng.bos.redhat.com 5.6.0-0.rc5.git0.1.fc33.aarch64

[root@hpe-apollo-cn99xx-14-vm-03 ~]# rpm -qa kexec-tools
kexec-tools-2.0.20-10.fc33.aarch64

Actual results:
Running kdumpctl restart on latest Fedora leading to failure message.

Expected results:
Running kdumpctl restart on latest Fedora should not lead to a failure message.

Comment 1 Kairui Song 2020-03-16 08:38:26 UTC
*** Bug 1812393 has been marked as a duplicate of this bug. ***

Comment 2 Bhupesh Sharma 2020-03-17 20:33:34 UTC
Tested the upstream patch (see <https://lists.fedoraproject.org/archives/list/kexec@lists.fedoraproject.org/thread/JAXGB7NP4QZ2MCS77OIRKZWLTVKAIALA/>), which seems to fixed the problem.

Provided my Tested and Reviewed-by for the same.

Thanks

Comment 3 Fedora Update System 2020-03-23 19:01:28 UTC
FEDORA-2020-47cd522de5 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-47cd522de5

Comment 4 Fedora Update System 2020-03-24 01:52:38 UTC
FEDORA-2020-d73f5db86c has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d73f5db86c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d73f5db86c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2020-03-24 09:41:23 UTC
FEDORA-2020-47cd522de5 has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-47cd522de5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-47cd522de5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2020-04-01 00:17:45 UTC
FEDORA-2020-d73f5db86c has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2020-04-01 16:32:34 UTC
FEDORA-2020-d73f5db86c has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2020-04-08 05:06:43 UTC
FEDORA-2020-47cd522de5 has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.