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
Set default entry to the BLS id instead of the entry index #1789
Conversation
|
Jenkins, test this please. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks a lot!
One small nitpick. There is a typo in the commit message:
So instead the default entry shold be explicit... -> So instead the default entry should be explicit
|
@jkonecny12 thanks, fixed the typo now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thank you!
|
@martinezjavier could you rebase this pull request to the |
The GRUB default boot entry is set to the default's entry index. This made sense on a non-BLS configuration because the entries where defined in the GRUB config file, so they had a strict definition order. But that's not the case on a BLS configuration, users can add or remove an entry by just dropping or removing files from the /boot/loader/entries dir. That means the default won't necessary be the installed kernel, but rather the BLS that's first in the sorted list of BLS snippets. So instead the default entry should be explicit and set to the BLS id of the default kernel (the machine ID followed by a dash and kernel version). That is also what is used when a new kernel is installed, so the initial grubenv should be consistent. Resolves: rhbz#1671047 Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
|
@poncovka done |
|
Jenkins, test this please. |
The GRUB default boot entry is set to the default's entry index. This made
sense on a non-BLS configuration because the entries where defined in the
GRUB config file, so they had a strict definition order.
But that's not the case on a BLS configuration, users can add or remove an
entry by just dropping or removing files from the /boot/loader/entries dir.
That means the default won't necessary be the installed kernel, but rather
the BLS that's first in the sorted list of BLS snippets.
So instead the default entry shold be explicit and be set to the BLS id of
the default kernel (the machine ID followed by a dash and kernel version).
That is also what is used when a new kernel is installed, so the initial
grubenv should be consistent.
Resolves: rhbz#1671047
Signed-off-by: Javier Martinez Canillas javierm@redhat.com