-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kdump to an NFS share require additional configuration (was: Consider adding NFS module to initramfs) #1729
Comments
While looking at something else, I found https://github.com/coreos/fedora-coreos-config/blob/testing-devel/overlay.d/05core/usr/lib/dracut/dracut.conf.d/coreos-omits.conf |
yes we explicitely omit it there that's why I opened this |
Discussed in the community meeting |
We should document how to workaround this issue for kdump. It should be possible to force the inclusion of the |
@travier another easy way is just to add Surprisingly |
Apparently this does not work and is tracked in https://issues.redhat.com/browse/RHEL-26114 |
We should add a test for this case. |
Might be needed related as well: https://gitlab.com/fedora/bootc/base-images/-/merge_requests/32 |
This way we have good coverage of most-used kdump features. Some context on the NFS kdump configuration coreos/fedora-coreos-tracker#1729
This way we have good coverage of most-used kdump features. Some context on the NFS kdump configuration coreos/fedora-coreos-tracker#1729
This way we have good coverage of most-used kdump features. Some context on the NFS kdump configuration: coreos/fedora-coreos-tracker#1729 This was previously merged in [1] then reverted in [2] because the nfs server container was not multi-arch, causing the pipeline to trip on it. It's also not functionning on systemd256 (so anything f41 and above), see [3] This requires coreos#3917 for the multi-arch container, and coreos#3921 [1] coreos@b10d8dc [2] coreos@af1468c [3] rhkdump/kdump-utils#52
This way we have good coverage of most-used kdump features. Some context on the NFS kdump configuration: coreos/fedora-coreos-tracker#1729 This was previously merged in [1] then reverted in [2] because the nfs server container was not multi-arch, causing the pipeline to trip on it. It's also not functionning on systemd256 (so anything f41 and above), see [3] This requires coreos#3917 for the multi-arch container, and coreos#3921 [1] coreos@b10d8dc [2] coreos@af1468c [3] rhkdump/kdump-utils#52
Hi @jbtrystram @travier, I'd like to fix this issue in kdump rhkdump/kdump-utils#31, but as I commented in rhkdump/kdump-utils#11 (comment), CoreOS's dracut conf may override most dracut varaiables. I suggest to rename them to something like "90-xxxx.conf". Or starting by dracut-104 dracut-ng/dracut-ng@ae81535, |
Hi, I think the dracut config file name issue should be a separate issue, here is a new one created for that: #1837 |
@licliu @daveyoung I've seen your comments here and in the kexdc-tools issue, but I am away from work for another week. Thanks for looking into that. |
@jbtrystram Thanks! |
Currently, the nfs kernel module is excluded from initramfs as we don't support root on NFS.
However, this prevents kdump to use NFS as a target for logs.
So maybe we could add back that module, or find a way to enable it only in the kdump case ?
See https://issues.redhat.com/browse/OCPBUGS-31755
The text was updated successfully, but these errors were encountered: