This came up on the fedora-users mailing list a couple of months ago. I believe it was discussed at "/boot problem", https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/G2MLXM6FE5NZTGHGCYFN3ZINHTXG3CQW/#AGAYJ46DHCZOFQLDHQNRUBSFTJCDODA6 (but the citation may be wrong).
It seems that once the rescue kernel is generated on system install, it is not regenerated again. It is not regenerated after a kernel update, and it is not regenerated after a dnf-system-upgrade.
I think a system upgrade should include a step to regenerate the rescue kernel.
I added these steps in one of my maintenance scripts to regenerate the rescue kernel whenever a new kernel appears.
rm -f /boot/*rescue* kernel-install add "$(uname -r)" "/lib/modules/$(uname -r)/vmlinuz"
Hrm, could you open a PR to add this to the post-installation steps please? We can get more folks to test/confirm the issue + fix and then merge the PR?
Metadata Update from @ankursinha: - Issue priority set to: waiting on external (was: awaiting triage) - Issue tagged with: help wanted, improvement, needs info, new change
@ankursinha,
could you open a PR to add this to the post-installation steps
Sure.
I have one more PR that addresses some questions that have been asked on the user's mailing list. Once that is merged (or rejected), I'll add something for this issue.
I don't want to make the change now because everything goes on the same (main) branch. I want to try to keep the commits separate.
Metadata Update from @noloader: - Issue untagged with: help wanted, improvement, needs info, new change - Issue priority set to: awaiting triage (was: waiting on external)
The pull request was made at https://pagure.io/fedora-docs/quick-docs/pull-request/659.
Feel free to tune it to your taste.
Login to comment on this ticket.