[06:09] <damaya> Hello, I'm running into this issue, https://discourse.maas.io/t/maas-2-5-wont-pxe-qlogic-10g-nic-hp-model-nc523sfp/313
[06:13] <damaya> I have a Broadcom NetXtreme II BCM57810 10 Gigabit Ethernet adapter, and we are running MAAS 2.8.1 (8567-g.c4825ca06). Every time we try to enlist a node using Legacy PXE boot, we run into this issue where as soon as PXE switches to HTTP, everything stops.
[06:13] <damaya> The screenshot here is exactly what is happening, https://discourse.maas.io/uploads/default/original/1X/3d89884a818429aa1942b94cf683d30700e8a634.jpg
[06:13] <damaya> That screenshot came from this thread: https://discourse.maas.io/t/pxe-not-working-after-upgrading-to-2-5-0/384/23
[06:14] <damaya> Is there any way to simply disable HTTP PXE and go back strictly to TFTP?
[06:15] <damaya> Or is there some sort of workaround here? I've searched launchpad / discourse and could only find unanswered threads.
[17:50] <mup> Bug #1888884 opened: Rescue fails on maas 2.3.6/2.3.5 with boot-kernel failed no such file or directory <MAAS:New> <https://launchpad.net/bugs/1888884>
[17:59] <mup> Bug #1888884 changed: Rescue fails on maas 2.3.6/2.3.5 with boot-kernel failed no such file or directory <MAAS:New> <https://launchpad.net/bugs/1888884>
[18:02] <mup> Bug #1888884 opened: Rescue fails on maas 2.3.6/2.3.5 with boot-kernel failed no such file or directory <MAAS:New> <https://launchpad.net/bugs/1888884>