I'm attaching a tarball with both the curtin-install-cfg.yaml and curtin-install.log files after a fresh installation, with the debugging feature you wanted activated.
Here's the output of "sudo efibootmgr -v" before the installation:
Note that installing requires either changing the boot order or deleting the "ubuntu" entry. I opted for the latter in this case. I can re-order the boot entries and try again, if you prefer. (I've done both in my testing, and both have the same result.)
Here's the same command's output immediately after the installation:
I'm attaching a tarball with both the curtin- install- cfg.yaml and curtin-install.log files after a fresh installation, with the debugging feature you wanted activated.
Here's the output of "sudo efibootmgr -v" before the installation:
$ sudo efibootmgr -v 0003,0004, 0005,0006, 0007,0008 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 1d76b9fa- 87f2-4ecf- ab6a-985c4a958d 6a)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 1d76b9fa- 87f2-4ecf- ab6a-985c4a958d 6a)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03) 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03)IbmS. ...h 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 1d76b9fa- 87f2-4ecf- ab6a-985c4a958d 6a)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03)IbmS. ....
BootCurrent: 0002
BootOrder: 0002,0001,
Boot0001* Hard Disk 0 FvVol(cdbb7b35-
Boot0002* PXE Network FvVol(cdbb7b35-
Boot0003 Enter Setup FvVol(cdbb7b35-
Boot0004 Boot Devices FvVol(cdbb7b35-
Boot0005 Boot Manager FvVol(cdbb7b35-
Boot0006 Setup FvVol(cdbb7b35-
Boot0007 Diagnostics FvVol(cdbb7b35-
Boot0008 Firmware Log FvVol(cdbb7b35-
Note that installing requires either changing the boot order or deleting the "ubuntu" entry. I opted for the latter in this case. I can re-order the boot entries and try again, if you prefer. (I've done both in my testing, and both have the same result.)
Here's the same command's output immediately after the installation:
$ sudo efibootmgr -v 0001,0003, 0004,0005, 0006,0007, 0008 7fb492e7- 7aac-4444- 896f-13532e2de1 f8,0x800, 0x100000) /File(\ EFI\ubuntu\ shimx64. efi) 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 1d76b9fa- 87f2-4ecf- ab6a-985c4a958d 6a)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 1d76b9fa- 87f2-4ecf- ab6a-985c4a958d 6a)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03) 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03)IbmS. ...h 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 1d76b9fa- 87f2-4ecf- ab6a-985c4a958d 6a)IbmS. .... 6833-4ed6- 9ab2-57d2acddf6 f0)/FvFile( 3cc3fdbd- 9658-47c1- b672-6263c1c7e4 03)IbmS. ....
BootCurrent: 0000
BootOrder: 0000,0002,
Boot0000* ubuntu HD(1,GPT,
Boot0001* Hard Disk 0 FvVol(cdbb7b35-
Boot0002* PXE Network FvVol(cdbb7b35-
Boot0003 Enter Setup FvVol(cdbb7b35-
Boot0004 Boot Devices FvVol(cdbb7b35-
Boot0005 Boot Manager FvVol(cdbb7b35-
Boot0006 Setup FvVol(cdbb7b35-
Boot0007 Diagnostics FvVol(cdbb7b35-
Boot0008 Firmware Log FvVol(cdbb7b35-