I'd (personally) be much more on board with a warning vs a hard block as
well.
The GRUB_FLAVOUR_ORDER issue was met with some resistance by both the
FIPs team and the OEM team. From what I gathered, GRUB_FLAVOUR_ORDER was
originally implement for the FIPS kernel, but later leveraged by OEM.
The O
> "Third-party drivers should not be installed on systems that will be
used for FIPS or the real-time kernel."
This may be sufficient. We're already talking about a fairly extreme
edge case here. The footprint of hardware that triggers the ubuntu-
drivers criteria that also is intended to use FIPS
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 ar
** Summary changed:
- Post-Install enablement of OEM-enabled devices will overwrite FIPs
+ FIPS/OEM installation compatibility is unclear to the end-user
** Description changed:
+ [Overall Summary]
+
+ Converting to cover all oem/fips compatibility issues with
+ ua/installers/update-manager. Th
** Also affects: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubun
5 matches
Mail list logo
