Skip to content
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

test: Enable kdump on Fedora 39 #19524

Merged
merged 1 commit into from
Oct 26, 2023

Conversation

martinpitt
Copy link
Member

@martinpitt martinpitt commented Oct 25, 2023

https://bodhi.fedoraproject.org/updates/FEDORA-2023-93fab3be92 disables the kdump/crashkernel configuration by default, so we need to go back to explicitly enabling it on Fedora 39 as well.

Unify this process on all Fedora versions, and use kdumpctl instead of messing around with grubby.


This blocks cockpit-project/bots#5442 . I'm triggering an extra fedora-39/expensive@bots#5442 test run against that image. This PR needs to land in lockstep with the image refresh.

@martinpitt
Copy link
Member Author

Ah yes, this check can't work on the current fedora-39 image, as the service does run by default. But I'd rather confirm this behaviour and land this PR in lockstep with the image refresh than relaxing the check.

@martinpitt
Copy link
Member Author

martinpitt commented Oct 25, 2023

Ech, SELinux... reported and naughtied.

and one more...

https://bodhi.fedoraproject.org/updates/FEDORA-2023-93fab3be92 disables
the kdump/crashkernel configuration by default, so we need to go back to
explicitly enabling it on Fedora 39 as well.

Unify this process on all Fedora versions, and use `kdumpctl` instead of
messing around with `grubby`.
@martinpitt martinpitt merged commit b74151b into cockpit-project:main Oct 26, 2023
97 of 99 checks passed
@martinpitt martinpitt deleted the enable-kdump branch October 26, 2023 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants