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 1536327 - Changing kdump location to"Use the setting in /etc/kdump.conf" failed with cockpit UI.
Summary: Changing kdump location to"Use the setting in /etc/kdump.conf" failed with co...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: pre-dev-freeze
: 7.7
Assignee: Martin Pitt
QA Contact: Jan Ščotka
URL:
Whiteboard:
Depends On:
Blocks: 1657383 1713633 1722722
TreeView+ depends on / blocked
 
Reported: 2018-01-19 07:17 UTC by Wei Wang
Modified: 2019-08-06 13:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1651691 (view as bug list)
Environment:
Last Closed: 2019-08-06 13:11:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
kdump setting picture (32.16 KB, image/png)
2018-01-19 07:17 UTC, Wei Wang 		no flags Details
log files (1.37 MB, application/x-gzip)
2018-01-19 07:20 UTC, Wei Wang 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2262 0 None None None 2019-08-06 13:11:45 UTC

Description Wei Wang 2018-01-19 07:17:34 UTC 
Created attachment 1383165 [details]
kdump setting picture

Description of problem:
Kdump can be located in Local/nfs/ssh with cockpit WebUI, local file-system is the default. If a user wants to use NFS/SSH for kdump, the location should be changed to "Use the setting in /etc/kdump.conf" with cockpit UI. But now apply changing failed, location still points to "locally in /var/crash", and vmcore files are still created in /etc/crash of localhost.

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.2-20180115.0
cockpit-ws-157-1.el7.x86_64
cockpit-dashboard-157-1.el7.x86_64
cockpit-bridge-157-1.el7.x86_64
cockpit-157-1.el7.x86_64
cockpit-storaged-157-1.el7.noarch
cockpit-system-157-1.el7.noarch
cockpit-ovirt-dashboard-0.11.4-0.1.el7ev.noarch
kernel-3.10.0-693.11.6.el7.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Clean install redhat-virtualization-host-4.2-20180115.0 with ks
2. Login to cockpit with root account
3. Go to Kernel Dump, open Crash dump location window
4. Apply the location to "Use the setting in /etc/kdump.conf" after setting nfs/ssh kdump in /etc/kdump.conf file
5. Check the setting in cockpit UI
6. Click "Test Configuration", then "Crash system"

Actual results:
After step 5, changing kdump location to"Use the setting in /etc/kdump.conf" failed, location still points to "locally in /var/crash".
After step 6, vmcore files are created in /etc/crash of localhost.

Expected results:
After step 5, the location should point to nfs/ssh address.
After step 6, vmcore files should be created in remote nfs/ssh server.


Additional info:
Comment 1 Wei Wang 2018-01-19 07:20:40 UTC 
Created attachment 1383166 [details]
log files
Comment 3 Martin Pitt 2018-10-17 07:59:22 UTC 
Confirmed, this also affects RHEL 8.
Comment 4 Martin Pitt 2018-10-17 08:10:29 UTC 
What does work is to edit /etc/kdump.conf, disable "path" and enable "nfs", then the Cockpit display immediately changes to "Remote over NFS". Then it's also possible to change the NFS location in the Cockpit UI.

But this already fails again when enabling "ssh" or "ext4" in kdump.conf, then the UI immediately switches back to "locally in /var/crash".

Also, changing the path in kdump.conf to "path /var/crash2" or something else isn't properly reflected in the UI. This only works in the Cockpit → config file direction.
Comment 5 Martin Pitt 2018-10-17 08:26:29 UTC 
I created https://projects.engineering.redhat.com/browse/COCKPIT-289 to revamp the design of this.
Comment 6 Martin Pitt 2018-11-20 14:22:16 UTC 
This got fixed in https://github.com/cockpit-project/cockpit/pull/10513
Comment 7 Martin Pitt 2019-01-05 18:10:55 UTC 
Landed in the upstream 7.7 branch.
Comment 12 errata-xmlrpc 2019-08-06 13:11:28 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, 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-2019:2262
Note You need to log in before you can comment on or make changes to this bug.