Comment 3 for bug 1978890

The issue arises with any package leveraging the GRUB_FLAVOUR_ORDER cfg. While originally requested by the FIPS team to ensure the env didn't accidentally boot to -generic, it was later implemented by the oem packages to ensure the oem kernel was preferred. The fact that it prefers oem when both are installed is only due to the cfg file names.

Subiquity just offers to install the oem packages if ubuntu-drivers finds a match on the hardware. The issue here is "Hey would you like to install some special hardware enablement drivers?" isn't necessarily indicative that you would no longer be able to install fips. This should more clearly convey what's happening here.

This issue has a capture of the some of the pages I'm talking about:
https://github.com/canonical/subiquity/pull/1196