Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2062297

Summary: Unclear error message when saving crash dump over NFS
Product: Red Hat Enterprise Linux 8 Reporter: Asaf Rachmani <arachman>
Component: cockpitAssignee: Martin Pitt <mpitt>
Status: CLOSED ERRATA QA Contact: Jan Ščotka <jscotka>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.6CC: mpitt
Target Milestone: rcKeywords: Triaged
Target Release: 8.7Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-269-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-08 10:48:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Error message screenshot
none
Error message screenshot none

Description Asaf Rachmani 2022-03-09 13:58:51 UTC
Description of problem:
Under "Crash dump location" when the location is "Remote over ssh"
the default value for the directory field is "/var/crash" and cannot be empty, if the path does not exist on the NFS, the operation will fail with the following error:
"Unable to apply settings: Error: systemd job RestartUnit ["kdump.service","replace"] failed with result failed"

Version-Release number of selected component (if applicable):
cockpit-260-1.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Launch cockpit "http://localhost:9090"
2. Set crash dump location to "Remote over NFS"
3. Use the default value in the Directory field and make sure it doesn't exist on the NFS
4. Test kernel dump

Actual results:
Getting an unclear error message - "Unable to apply settings: Error: systemd job RestartUnit ["kdump.service","replace"] failed with result failed"

Expected results:
Get a clear error message

Additional info:
See also bug 1713633#c30

Comment 1 Asaf Rachmani 2022-03-09 14:01:40 UTC
Created attachment 1864913 [details]
Error message screenshot

Comment 2 Asaf Rachmani 2022-03-09 14:03:18 UTC
Created attachment 1864914 [details]
Error message screenshot

Comment 3 Martin Pitt 2022-04-04 06:36:26 UTC
I improved this in https://github.com/cockpit-project/cockpit/pull/17214 , the dialog now shows the kdump.service journal to give more details. kdump's error message is still confusing though, I filed bug 2071529 about that. When that is fixed, it should be clear enough. Thanks!

Comment 12 errata-xmlrpc 2022-11-08 10:48:03 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 (cockpit 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-2022:7718