Bug 1536327
| Summary: | Changing kdump location to"Use the setting in /etc/kdump.conf" failed with cockpit UI. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Wei Wang <weiwang> | ||||||
| Component: | cockpit | Assignee: | Martin Pitt <mpitt> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Jan Ščotka <jscotka> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 7.4 | CC: | bugs, cshao, huzhao, qiyuan, rbarry, yaniwang, ycui | ||||||
| Target Milestone: | pre-dev-freeze | ||||||||
| Target Release: | 7.7 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1651691 (view as bug list) | Environment: | |||||||
| Last Closed: | 2019-08-06 13:11:28 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1657383, 1713633, 1722722 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1383166 [details]
log files
Confirmed, this also affects RHEL 8. 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. I created https://projects.engineering.redhat.com/browse/COCKPIT-289 to revamp the design of this. This got fixed in https://github.com/cockpit-project/cockpit/pull/10513 Landed in the upstream 7.7 branch. 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 |
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: