Comment 51 for bug 1789650

I've run a new series of tests with the latest version. Here are the results:

- When installing with no ubuntu entry, a new ubuntu entry
  is created at the END of the boot list.
- When an existing ubuntu entry is first in the boot list,
  the ubuntu entry remains (or is re-created in) first
  place.
- When an existing ubuntu entry is second in the boot list
  (after the PXE-boot entry), ubuntu remains second in
  the boot list.
- When an existing ubuntu entry is last in the boot list,
  ubuntu remains last in the boot list.

To test the second condition, I wiped the partition table, thus causing a failure of the existing ubuntu entry; the firmware failed over to PXE-booting.

I'm attaching the /var/log/maas/rsyslog/oil-drapion/2020-07-27/messages file, which should hold logs of all these deployments. (Note that I tested most conditions twice, once with and once without wiping the disk partition table with "sudo sgdisk -Z /dev/sda". I saw no effect from this practice, except that installing with the ubuntu entry first without wiping the partition table is impossible -- or it would require some other workaround, like doing a one-time manual PXE boot, which I did not test.)