-
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
[rawhide] kdump.crash fails missing makedumpfile #1692
Comments
regarding https://src.fedoraproject.org/rpms/kexec-tools/c/ec3bccdf326881decd13f0ac7b4558f4a22875bd?branch=rawhide it looks like now we need to specify the |
dustymabe
changed the title
[rawhide] ext.config.kdump.crash test failing
[rawhide] kdump.crash fails missing makedumpfile
Mar 15, 2024
dustymabe
added a commit
to dustymabe/fedora-coreos-config
that referenced
this issue
Mar 15, 2024
This was made into a subpackage, but is required for kdump to work. See coreos/fedora-coreos-tracker#1692
dustymabe
added a commit
to dustymabe/fedora-coreos-config
that referenced
this issue
Mar 15, 2024
This was made into a subpackage, but is required for kdump to work. See coreos/fedora-coreos-tracker#1692
dustymabe
added a commit
to coreos/fedora-coreos-config
that referenced
this issue
Mar 16, 2024
This was made into a subpackage, but is required for kdump to work. See coreos/fedora-coreos-tracker#1692
aaradhak
pushed a commit
to aaradhak/fedora-coreos-config
that referenced
this issue
Mar 18, 2024
This was made into a subpackage, but is required for kdump to work. See coreos/fedora-coreos-tracker#1692
We should be able to close this with coreos/fedora-coreos-config#2903 now merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On the
kexec-tools 2.0.28-4.fc40 -> 2.0.28-5.fc41
transition theext.config.kdump.crash
is now failing.This happened in https://jenkins-fedora-coreos-pipeline.apps.ocp.fedoraproject.org/blue/organizations/jenkins/build/detail/build/2385
The failure looks like:
Looking at the logs:
The text was updated successfully, but these errors were encountered: