I've done 2 more tests - confirming the bug is constrained to HTTP boot.
1. Boot in PXE mode over HPE Ethernet 1Gb 4-port 366FLR Adapter - NIC (PXE IPv4). This works fine with:
configfile (pxe)/grub/grub.cfg-default-amd64
2. Boot in HTTP mode over HPE Ethernet 1Gb 4-port 366FLR Adapter - NIC (HTTP(S) IPv4). This does not work well as mentioned in the bug:
I can see:
2020-10-16 13:12:26 provisioningserver.rackdservices.http: [info] grub/grub.cfg requested by 10.216.240.37
Then the server drops to grub prompt.
Grub environment consult attached screenshot.
I can see that:
- there is no (pxe) variable
- net_default_server is set to 10.216.240.1:5248
- prefix is set to (http,to 10.216.240.1:5248)/grub
- pxe_default_server is set to 10.216.240.1:5248
- root is set to http,10.216.240.1:5248
That explains, why in this case, the server attempts to load (tftp,10.216.240.1:5248). It derives this from the net_default_server.
This does not have a chance to work as tftp is not listening on port 5248.
I've done 2 more tests - confirming the bug is constrained to HTTP boot.
1. Boot in PXE mode over HPE Ethernet 1Gb 4-port 366FLR Adapter - NIC (PXE IPv4). This works fine with: grub.cfg- default- amd64
configfile (pxe)/grub/
2. Boot in HTTP mode over HPE Ethernet 1Gb 4-port 366FLR Adapter - NIC (HTTP(S) IPv4). This does not work well as mentioned in the bug:
I can see: ver.rackdservic es.http: [info] grub/grub.cfg requested by 10.216.240.37
2020-10-16 13:12:26 provisioningser
Then the server drops to grub prompt.
Grub environment consult attached screenshot.
I can see that: 240.1:5248) /grub 216.240. 1:5248
- there is no (pxe) variable
- net_default_server is set to 10.216.240.1:5248
- prefix is set to (http,to 10.216.
- pxe_default_server is set to 10.216.240.1:5248
- root is set to http,10.
That explains, why in this case, the server attempts to load (tftp,10. 216.240. 1:5248) . It derives this from the net_default_server.
This does not have a chance to work as tftp is not listening on port 5248.