Public bug reported:
We noticed recently that MAAS apparently no longer marks MBR OS
partitions bootable. Most of the time this does not cause a problem
because MAAS boots happen via PXE, and as well as this not every
firmware cares about this flag, so even in the case of a direct disk
boot this may not cause a problem.
However, we discovered recently while recovering from an incident that
some of our machines (Hewlett-Packard ProLiant DL380p Gen8 in this case)
do care about this, and if MAAS is unavailable they will refuse to boot
completely. (Canonical employees can review this incident to understand
its impact by looking for the leyak incident on 2018-09-26.)
One configuration we've observed this is on bionic deployed by maas
2.3.4-6504-gac6a15b-0ubuntu1~16.04.1. We've also observed this on
xenial machines deployed by 1.9.5+bzr4599-0ubuntu1~14.04.3 (the incident
mentioned above). We inspected some other older machines that were also
installed a few years ago by the same maas as installed the incident-
affected machines, and they *do* have the partition bootable flag set,
although it may be hard to work out exactly how they were installed and
what versions of MAAS this was.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801810
Title:
MBR OS partition is not marked bootable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1801810/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
