Where is the best place to report a bug with the upgrade from 10.0 to 10.1?
It occurs only when the usbguard package is installed. The selinux policy fails to rebuild and Rocky boots in a read only mode unless selinux is set to permissive in the kernel options. I think it’s an issue with the usbguard package instead of Rocky.
Greetings @EchoFable ! Welcome to the community.
I don’t have access to a physical machine 10.0 at the moment, so I tossed this test at a VM. Couldnt’t reproduce. So I went looking for package changes… usbguard package hasn’t changed between 10.0 and 10.1 - still usbguard-1.1.3-6 from 2025-May-23.
So this has me wondering is this something that happens on physical gear? Is there something else going on? Do I maybe need more configuration? Dunno…
I’m happy to look at this when I get back to my home lab from travels (but that’s going to be a while…). Maybe someone else has a better idea of what’s going on?
Thanks for the problem report!
I found this behaviour with a VM (usbguard was just lazily installed on everything VMs included), specifically a minimal install but I’ve tried today to reproduce with a different hypervisor and haven’t been successful. I’ll have a look next week and reproduce again with the other hypervisor and provide more information related to the error seen.
It’s very odd that I now can’t reproduce with an alternative hypervisor.