Hiya @george1421. First, thanks for your time thus far and thank you for the background/context. I truly was not aware the way we are using FOG was an edge case so I appreciate the extra help.
I can confirm I’ve put the bzImage you provided in place but continue to hit the same screen. Taking a step back, here is some additional context from my end:
This is a new deployment and new environment. I am using dnsmasq for DNS and DHCP on a server, “soko01” at 10.20.192.11 The rest of the servers of this type are still pointed at a MaaS instance so I have some chain loading going on in dnsmasq to target one server, “trial194” that I am attempting to capture a FOG image from. The rest are still pointed at MaaS. MaaS lives on soko02 at 10.20.192.12 FOG lives on soko03 at 10.20.192.13Here is my dnsmasq conf
########################## ### maas configuration ### ########################## dhcp-match=set:pxearch0,option:client-arch,00:00 dhcp-match=set:pxearch7,option:client-arch,00:07 dhcp-match=set:pxearch10,option:client-arch,00:10 dhcp-match=set:pxearch9,option:client-arch,00:09 dhcp-match=set:pxearch8,option:client-arch,00:08 dhcp-match=set:pxearch13,option:client-arch,00:13 dhcp-match=set:pxearch0c,option:client-arch,00:0c dhcp-match=set:pxearch0e,option:client-arch,00:0e dhcp-match=set:pxearch1f,option:client-arch,00:1f dhcp-match=set:pxearch20,option:client-arch,00:20 dhcp-match=set:pxearch11,option:client-arch,00:0b dhcp-boot=tag:maas,tag:pxearch0,lpxelinux.0,soko02,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch7,bootx64.efi,0.0.0.0,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch10,http://10.20.192.12:5248/images/bootx86.efi,soko02,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch9,bootx64.efi,0.0.0.0,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch8,bootaa64.efi,0.0.0.0,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch13,http://10.20.192.12:5248/images/bootaa64.efi,soko02,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch0c,bootppc64.bin,soko02,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch0e,pxelinux.0,soko02,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch1f,boots390x.bin,soko02,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch20,s390x_partition/maas,soko02,10.20.192.12 dhcp-boot=tag:maas,tag:pxearch11,http://10.20.192.12:5248/images/grubaa64.efi,soko02,10.20.192.12 ######################### ### fog configuration ### ######################### # FOG PXE (soko03 / 10.20.192.13) # Detect iPXE dhcp-userclass=set:ipxe,iPXE dhcp-vendorclass=set:ipxe,iPXE dhcp-match=set:ipxe,175 # FOG stage 1 (only if NOT already iPXE) dhcp-boot=tag:fog,tag:!ipxe,tag:pxearch0,undionly.kpxe,soko03,10.20.192.13 dhcp-boot=tag:fog,tag:!ipxe,tag:pxearch0e,undionly.kpxe,soko03,10.20.192.13 dhcp-boot=tag:fog,tag:!ipxe,tag:pxearch7,snponly.efi,10.20.192.13,10.20.192.13 dhcp-boot=tag:fog,tag:!ipxe,tag:pxearch9,snponly.efi,10.20.192.13,10.20.192.13 # iPXE stage: set BOTH bootfile AND next-server dhcp-boot=tag:fog,tag:ipxe,http://10.20.192.13/fog/service/ipxe/boot.php,soko03,10.20.192.13 # A MaaS-provisioned host dhcp-host=set:maas,set:front,90:5a:08:77:62:02,10.20.193.193,trial193.front.sepia.ceph.com # A FOG-provisioned host dhcp-host=set:fog,set:front,90:5a:08:77:63:36,10.20.193.194,trial194.front.sepia.ceph.comThe autoexec.ipxe file I am serving
root@soko03:/var/www/html/fog/service/ipxe# cat /tftpboot/autoexec.ipxe #!ipxe dhcp chain http://10.20.192.13/fog/service/ipxe/boot.php || shellHere is the screen I am getting right before the DDP package error
iKVM_capture3.jpg
Which signals to me that it’s getting the bzImage file okay. If I load http://10.20.192.13/fog/service/ipxe/boot.php, it looks normal.
What should I check next?