Not sure about where or how far to push ubuntu down the list, especially when a system has 2 or more potential bootable network devices.
I have run into the same thing with MaaS setup.
- 2.8.1 MaaS
- Supermicro in UEFI mode
- two networks connected (in a LAG)
The problem is that after a deploy, the first network is brought ahead of 'ubuntu' so the boot order is UEFI0,ubuntu,UEFI1,UEFI2,UEFI3
And since MaaS can set either 0 or 1 to be PXE boot, on the systems where network 1 is set for PXE then no chance to boot from network -- the local storage is ahead.
Perhaps our workaround is to suppress the ubuntu(disk) entry completely?
Not sure about where or how far to push ubuntu down the list, especially when a system has 2 or more potential bootable network devices.
I have run into the same thing with MaaS setup.
- 2.8.1 MaaS
- Supermicro in UEFI mode
- two networks connected (in a LAG)
The problem is that after a deploy, the first network is brought ahead of 'ubuntu' so the boot order is UEFI0,ubuntu, UEFI1,UEFI2, UEFI3
And since MaaS can set either 0 or 1 to be PXE boot, on the systems where network 1 is set for PXE then no chance to boot from network -- the local storage is ahead.
Perhaps our workaround is to suppress the ubuntu(disk) entry completely?