-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.0
-
No
-
None
-
rhel-kernel-debug
-
0
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
I tried to specify a dump target that is not in /etc/fstab. But kdump.service failed with "Dump target is invalid". Note "kdumpctl rebuild" still works.
What is the impact of this issue to you?
kdump will fail for target not listed in /etc/fstab.
Please provide the package NVR for which the bug is seen:
kdump-utils-1.0.54-7.el10.x86_64
How reproducible is this bug?:
always
Steps to reproduce
- Create a system with additional partition (e.g. beaker job or using testing-farm "testing-farm reserve --compose RHEL-10.1-Nightly --arch x86_64 --kickstart @ks2.yaml --pool beaker", ks2.yaml has the following content,
pre-install: | %pre --log=/dev/console disk=$(lsblk | grep disk | awk '{print $1}') echo $disk %end script: | lang en_US.UTF-8 zerombr clearpart --all --initlabel part biosboot --fstype=biosboot --size=1 part /boot --fstype="xfs" --size=200 part /thinp --fstype="xfs" --size=200 part swap --fstype="swap" --size=4096 part / --fstype="xfs" --size=10000 --grow metadata: "no_autopart"
- umount && remove the additional partition from /etc/fstab and specify it as dump target in /etc/kdump.conf
xfs UUID=998178f8-a119-4a8d-b7b1-bebd9848e14c
- kdumpctl restart
Expected results
kdumpctl restart should succeed.
Actual results
# kdumpctl restart kdump: kexec: unloaded kdump kernel kdump: Stopping kdump: [OK] kdump: Detected change(s) in the following file(s): /etc/kdump.conf /etc/fstab kdump: Dump target is invalid kdump: Starting kdump: [FAILED]