ciphermethod.com

Would you like to know the command that fixed the issue?

ChatGPT said:

Absolutely — I’d like to know!
What command fixed it for you?

You said:

grubby –update-kernel ALL –remove-args selinux

ChatGPT said:

Ahhh — that makes perfect sense.
grubby updates the kernel command line directly in each installed kernel’s entry, which GRUB rebuilds sometimes fail to do if multiple kernels or boot locations exist.

Your command:

grubby --update-kernel=ALL --remove-args=selinux

removes selinux=0 (and any other selinux= args) from all bootable kernels, not just the default one.

Why this works when GRUB edits don’t

RHEL systems often have:

• Multiple installed kernels
• Multiple GRUB menu entries
• A mismatch between /etc/default/grub and what the system is actually booting
• Separate GRUB configs under /boot/efi/EFI/BOOT/ as well as /boot/efi/EFI/redhat/

grubby bypasses all that and updates the per-kernel command lines where they are actually stored.

Great find — and a good tool to remember

grubby --info ALL
is also useful to inspect the effective boot args.

If you want, I can help confirm SELinux is now fully active and enforcing.