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.
Bug 2140721 - [Kdump] Failed to generate the vmcore over NFS with dracut_args option.
Summary: [Kdump] Failed to generate the vmcore over NFS with dracut_args option.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kexec-tools
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Coiby
QA Contact: xiaoying yan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-07 17:53 UTC by rcheerla
Modified: 2023-11-07 11:18 UTC (History)
5 users (show)

Fixed In Version: kexec-tools-2.0.25-14.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-07 08:51:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-138560 0 None None None 2022-11-07 18:01:35 UTC
Red Hat Product Errata RHBA-2023:6594 0 None None None 2023-11-07 08:51:42 UTC

Description rcheerla 2022-11-07 17:53:12 UTC 
Description of problem: Vmcore generation is getting failed when using the persistent NIC device name. 

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

kernel-5.14.0-162.6.1.el9_1.x86_64
kexec-tools-2.0.24-5.el9.x86_64
NetworkManager-1.40.0-1.el9.x86_64
nfs-utils-2.5.4-15.el9.x86_64

How reproducible: Always


Steps to Reproduce:
1. Configure the kdump to dump the vmcore file over remote system via NFS.

$ grep -v "#" /etc/kdump.conf 
auto_reset_crashkernel yes
core_collector makedumpfile -l --message-level 7 -d 31
dracut_args --mount "<NFS-server-ip>:/var/crash /mnt nfs defaults"
path /

2. Then add the udev rules to change the NIC name to eth0. 

cat /etc/udev/rules.d/60-persistent-net.rules 
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:c0:5b:eb", ATTR{type}=="1", KERNEL=="*", NAME="eth0"

3. Add the network configuration file associated to eth0 

cat /etc/NetworkManager/system-connections/eth0.nmconnection 
[connection]
id=eth0
uuid=3a4b8d71-1ce5-4365-a334-106f4bd8332d
type=ethernet
interface-name=eth0

[ethernet]

[ipv4]
method=auto

[ipv6]
addr-gen-mode=eui64
method=auto

[proxy]

4. Reboot the system. 

5. Check NIC naming by running `$ ip a s` command, it should be eth0 

6. Then test the kdump by running `$ echo c > /proc/sysrq-trigger` command. 


Actual results:

[    3.813198] systemd[1]: dracut mount hook was skipped because all trigger condition checks failed.
[    4.217334] IPv6: ADDRCONF(NETDEV_CHANGE): kdump-eth0: link becomes ready
[    5.159760] mount[446]: mount.nfs: Protocol not supported
[    5.164502] systemd[1]: mnt.mount: Mount process exited, code=exited, status=32/n/a
[    5.167616] systemd[1]: mnt.mount: Failed with result 'exit-code'.
[FAILED] Failed to mount /mnt.
See 'systemctl status mnt.mount' for details.


Expected results:  Kdump should work.


Additional info: I have confirmed that the kdump over NFS is working fine with default NIC name.
Comment 4 Coiby 2022-11-10 06:19:03 UTC 
Hi,

This issue has nothing to do with using persistent NIC name.  You may have manually mounted nfs target when not using persistent name before building the kdump initrd. 

The root cause is you use 'dracut_args --mount "<NFS-server-ip>:/var/crash /mnt nfs defaults"' which makes dracut fail to install required kernel drivers like nfs. 

You should use "nfs <NFS-server-ip>:/var/crash" instead and kexec-tools will automatically mount the nfs target (which makes sure drivers like nfs will be installed) and also some sanity checks. So I don't think this is a bug.
Comment 11 Coiby 2023-03-21 08:04:06 UTC 
https://gitlab.com/redhat/centos-stream/rpms/kexec-tools/-/merge_requests/131
Comment 18 errata-xmlrpc 2023-11-07 08:51:26 UTC 
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 (kexec-tools 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/RHBA-2023:6594
Note You need to log in before you can comment on or make changes to this bug.