Comment 8 for bug 1642298

I've uploaded curtin - 0.1.0~bzr432-0ubuntu1 to ppa:raharper/bugfixes which includes execution tracing during grub install, specifically dumping out efibootmgr output before and after the grub-install command. This should help see where (if any) change to the boot order is happening.

(Note this is output from a VM install which we explicity request nvram updates)

[ 124.997847] cloud-init[1431]: curtin uefi: installing grub-efi-amd64 to: /boot/efi
[ 125.001034] cloud-init[1431]: + echo before grub-install efiboot settings
[ 125.004153] cloud-init[1431]: before grub-install efiboot settings
[ 125.006996] cloud-init[1431]: + efibootmgr
[ 125.007626] cloud-init[1431]: Timeout: 0 seconds
[ 125.009512] cloud-init[1431]: BootOrder: 0000
[ 125.010146] cloud-init[1431]: Boot0000* UiApp
[ 125.012019] cloud-init[1431]: + dpkg-reconfigure grub-efi-amd64

<snip grub-install --help parsing output>

[ 125.604192] cloud-init[1431]: + grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ubuntu --recheck
[ 125.606094] cloud-init[1431]: Installing for x86_64-efi platform.
[ 125.996485] cloud-init[1431]: Installation finished. No error reported.
[ 125.998933] cloud-init[1431]: + echo after grub-install efiboot settings
[ 126.000287] cloud-init[1431]: after grub-install efiboot settings
[ 126.001402] cloud-init[1431]: + efibootmgr
[ 126.003282] cloud-init[1431]: Timeout: 0 seconds
[ 126.003947] cloud-init[1431]: BootOrder: 0001,0000
[ 126.004926] cloud-init[1431]: Boot0000* UiApp
[ 126.005721] cloud-init[1431]: Boot0001* ubuntu