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.

This bug was initially created as a copy of Bug #2071529

I am copying this bug because: 



Description of problem: This is a spin-off of cockpit bug 2062297. When kdump is configured with some NFS location, like

  nfs 10.111.113.2:/srv/kdump
  path dumps

and the remote directory does not exist on the server (i.e. /srv/kdump/ does not have a "dumps" directory), kdump.service fails with a confusing error message.


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

kexec-tools-2.0.22-7.fc35.x86_64

How reproducible: Always


Steps to Reproduce:
1. Set up NFS location for non-existing directory, see above.
2. Start kdump.service

Actual results: kdump.service fails with error:

    kdumpctl[2172]: kdump: Dump path "/tmp/mkdumprd.ftWhOF/target/dumps" does not exist in dump target "10.111.113.2:/srv/kdump"

This is confusing -- Of course /tmp/mkdumprd.ftWhOF/ does not exist on the server. That's the local temporary mount point.

Expected results: Skip the local mount prefix. Should be like this:

    kdumpctl[2172]: kdump: Dump path "dumps" does not exist in dump target "10.111.113.2:/srv/kdump"

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:2463