-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
rhel-9.5
-
No
-
Moderate
-
rhel-anaconda
-
None
-
False
-
False
-
Yes
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
None
What were you trying to do that didn't work?
Installing an rpm-ostree system that uses bootupd with anaconda / kickstart, using
`bootloader --password=...`
What is the impact of this issue to you?
The password is silently ignored, using grub2-set-password is not enough
Please provide the package NVR for which the bug is seen:
bootupd-0.2.25-1.el9.x86_64
(I'm using bootupd from CentOS stream)
How reproducible is this bug?:
100%
Steps to reproduce
1) install an ostree payload that has bootupd with anaconda
2) look at /boot/grub2/grub2.cfg and /boot/grub2/user.cfg
Expected results
It works !
Actual results
- /boot/grub2/user.cfg is not created (it should contain `GRUB2_PASSWORD=...`)
- the generated /boot/grub2/grub2.cfg does source user.cfg but is missing the logic to use GRUB2_PASSWORD (~ /etc/grub.d/01_users)
An important note, we MUST NOT use user.cfg as a generic config file, as grub2-set-password overwrite file