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 2004041 - kdump configuration wizard must ask for path for NFS
Summary: kdump configuration wizard must ask for path for NFS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.6
Assignee: Martin Pitt
QA Contact: Jan Ščotka
URL:
Whiteboard:
: 1724107 (view as bug list)
Depends On:
Blocks: 1713633
TreeView+ depends on / blocked
 
Reported: 2021-09-14 12:18 UTC by Lev Veyde
Modified: 2022-05-10 16:30 UTC (History)
1 user (show)

Fixed In Version: cockpit-255-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 15:18:37 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 Bugzilla 1724107 1 medium CLOSED Kdump service is stopped with an error when changing crash dump location to "Remote over NFS" in cockpit UI 2022-03-22 10:51:31 UTC
Red Hat Issue Tracker RHELPLAN-97090 0 None None None 2021-09-14 12:19:02 UTC
Red Hat Product Errata RHSA-2022:2008 0 None None None 2022-05-10 15:18:52 UTC

Internal Links: 1724107

Description Lev Veyde 2021-09-14 12:18:30 UTC 
Description of problem:

When configuring kdump, in case NFS remote configuration is used, cockpit only asks for the NFS mount point, but not the path - the directory to used under that mount point.
That unlike the local and SSH configuration types, for which cockpit asks for path/directory.

Moreover, the created configuration that cockpit puts in /etc/kdump.conf in case of NFS, contains only the "nfs" parameter.
That causes the default of /var/crash to be used for path.
Thus "var/crash" directory stucture must exists under the mount point, or the kdump service will fail to start.

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

How reproducible:
100%

Steps to Reproduce:
1. Login into cockpit web interface
2. Select Kernel Dump tab
3. Switch to Remote over NFS
4. Note that only "Mount" field is available
5. Trying to setting a valid mount point will either accept the configuration but cause the kdump service to fail or fail to accept the valid mount point, with an error.
6. Clicking on Apply button again will accept the configuration, but the kdump service will fail.

Actual results:
cockpit asks only for NFS mount point for kdump remote NFS configuration

Expected results:
Cockpit must ask for path/directory to be used under the NFS mount point, and include it in the kdump configuration file.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1724107
Comment 1 Lev Veyde 2021-09-14 12:27:17 UTC 
Also it means that cockpit will need to verify that <NFS mountpoint>/<path> exists, instead of just <NFS mountpoint>.

And as a side note it will be great if cockpit also verifies that the target is writable, and files can be created there.
Comment 2 Martin Pitt 2021-09-15 10:02:45 UTC 
Confirmed, thanks for the report! That's a really strange configuration API.. The "nfs" option already specifies a remote mount point, so appending "path" to that is just rather unintuitive.

I am currently working on an end-to-end integration test for this and testing NFS dumps. I can confirm this bug, but I can't get NFS dumps to work at all in RHEL 8.5 and Fedora 35. I filed bug 2004434 about this.
Comment 3 Martin Pitt 2021-09-23 09:26:35 UTC 
Fixed upstream in https://github.com/cockpit-project/cockpit/pull/16385

Jan: This has an integration test, but it does not run in gating as it can't be made non-destructive (the kdump test has to reboot)
Comment 4 Martin Pitt 2021-09-23 09:29:04 UTC 
*** Bug 1724107 has been marked as a duplicate of this bug. ***
Comment 5 Martin Pitt 2021-09-23 09:43:50 UTC 
Jan: I updated the PR to cover the UI → kdump.conf parts in TestKdump.testConfiguration() (which runs in gating). This should already suffice for this bug, and the upstream CI test can make sure it works end-to-end.
Comment 6 Lev Veyde 2021-10-03 07:38:10 UTC 
(In reply to Martin Pitt from comment #2)
> Confirmed, thanks for the report! That's a really strange configuration
> API.. The "nfs" option already specifies a remote mount point, so appending
> "path" to that is just rather unintuitive.
> 
> I am currently working on an end-to-end integration test for this and
> testing NFS dumps. I can confirm this bug, but I can't get NFS dumps to work
> at all in RHEL 8.5 and Fedora 35. I filed bug 2004434 about this.

Yes, agreed, it's indeed counter intuitive, and not what one may expect - it becomes clear that path is still used for NFS only after carefully reading the kdump docs/conf file comments.
And that probably mostly happens only after one has a configuration issue...

Anyway, glad that we caught and fixed the issue.
Comment 7 Martin Pitt 2021-10-03 17:21:53 UTC 
> Yes, agreed, it's indeed counter intuitive, and not what one may expect

On second thought it actually makes sense. I guess I am way too much used to scp/rsync copying, and not enough with NFS. The NFS share is indeed server:/exported/location, not any arbitrary subpath of that.

Anyway, the fix is in Fedora now, we'll package the current version for 8.6 soon.
Comment 14 errata-xmlrpc 2022-05-10 15:18:37 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 (Moderate: cockpit security, 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/RHSA-2022:2008
Note You need to log in before you can comment on or make changes to this bug.