-
Notifications
You must be signed in to change notification settings - Fork 192
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
Wrong bootloader name after update from older deployment #1343
Comments
My initial worry is that this was some sort of core issue with say the grub rework that partially landed in f28, but I'm not immediately reproducing an issue like this in some local testing at least with FAH. (Random aside, you don't need to use How reproducible is this? If you e.g. |
Ok. Redoing the steps after I suppose it only happens after updating (without cleanup) and then installing/uninstalling something. |
When comparing deployments to determine whether we need a new bootversion, we should also check whether the commit "version" metadata is the same. Otherwise, we may end up with the a bootconfig whose `title` includes a version that doesn't match the one from the deployment checksum. Closes: coreos/rpm-ostree#1343
Thanks for filing this! I've definitely hit it myself before, but never bothered to look deeper into it. This is actually a libostree issue; I submitted a patch: ostreedev/ostree#1556. Though I think it's fine leaving the issue here. |
Fedora 28 Atomic Workstation, x86_64, EFI bootloader
I had
28.20180415.n.0
and28.20180417.n.0
deployments, the latter with layeredmesa-libGL
andmesa-libEGL
packages. I've rebooted into28.20180415.n.0
, didThen rebooted. The newer bootloader entry is still called
28.20180417.n.0
, but it loads the new28.20180419.n.0
deployment correctly.The text was updated successfully, but these errors were encountered: