Bug 2004041
| Summary: | kdump configuration wizard must ask for path for NFS | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Lev Veyde <lveyde> |
| Component: | cockpit | Assignee: | Martin Pitt <mpitt> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Ščotka <jscotka> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.4 | CC: | weiwang |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | 8.6 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cockpit-255-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-10 15:18:37 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: | 1713633 | ||
|
Description
Lev Veyde
2021-09-14 12:18:30 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. 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. 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) *** Bug 1724107 has been marked as a duplicate of this bug. *** 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. (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. > 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.
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 |