# Rhel\_system\_roles.bootloader - need to manually rebuild grub after configuration?

**URL:** <https://forum.ansible.com/t/rhel-system-roles-bootloader-need-to-manually-rebuild-grub-after-configuration/44593>\
**Category:** Get Help\
**Tags:** rhel, aap, linux-system-roles\
**Created:** [October 1, 2025, 8:42am UTC](https://forum.ansible.com/t/rhel-system-roles-bootloader-need-to-manually-rebuild-grub-after-configuration/44593 "2025-10-01T08:42:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jerry](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jerry/32/2572_2.png) [@Jerry](https://forum.ansible.com/u/Jerry)\
**Post date:** [October 1, 2025, 8:42am UTC](https://forum.ansible.com/t/rhel-system-roles-bootloader-need-to-manually-rebuild-grub-after-configuration/44593/1 "2025-10-01T08:42:30Z")

</div>

**rhel\_system\_roles.bootloader - need to manually rebuild grub configuration?**  
Hi!  
I am using rhel\_system\_roles.bootloader to configure a bootloader password.  
I notice that when I run the role it configures /boot/grub2/user.cfg with a GRUB2\_PASSWORD but it does not rebuild the grub configuration which means that the changes does not take effect. Is this by design? The documentation does not mention anything about it as I can see.

To rebuild the grub configuration I had to manually run:

```auto
grub2-mkconfig -o /boot/grub2/grub.cfg

```

This has been tested using version collection version 1.95.7 on RHEL9.6.  
I am using below variables as input to the role:

```auto
# Note: bootloader_pw is defined in AAP Credential Bootloader_pw
bootloader_password: "{{ bootloader_pw }}"
bootloader_reboot_ok: true

```

#rhel-system-roles

---

<div class="post-metadata">

**Author:** ![nbeernink](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nbeernink/32/9890_2.png) [@nbeernink](https://forum.ansible.com/u/nbeernink)\
**Post date:** [June 5, 2026, 12:12pm UTC](https://forum.ansible.com/t/rhel-system-roles-bootloader-need-to-manually-rebuild-grub-after-configuration/44593/2 "2026-06-05T12:12:37Z")

</div>

Hi Jerry, sorry for resurrecting this post from the dead, but did you ever get an answer to this?

Ran into exactly the same issue and found your post on the forum.

If rhel\_system\_roles.bootloader claims to manage the bootloader it should include a step that does that, else what’s the point? 🙂

Also opening a Red Hat case on this to see what’s “the official word” is.

Checked [the issues on the upstream linux-system-roles/bootloader](https://github.com/linux-system-roles/bootloader/) but found no mention of it.

---

<div class="post-metadata">

**Author:** ![nbeernink](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nbeernink/32/9890_2.png) [@nbeernink](https://forum.ansible.com/u/nbeernink)\
**Post date:** [July 12, 2026, 7:28am UTC](https://forum.ansible.com/t/rhel-system-roles-bootloader-need-to-manually-rebuild-grub-after-configuration/44593/3 "2026-07-12T07:28:22Z")

</div>

@Jerry were you also using this role on RHEL images built with image-builder? We are and apparently image-builder generates images that have a bug in grub.cfg and apparently that’s the reason the password is not being picked up.

While we wait on an official fix, we wrapped the role in a wrapper role that runs the command you mentioned; `grub2-mkconfig -o /boot/grub2/grub.cfg`