cobbler
cobbler copied to clipboard
Cannot PXE boot with new Cobbler install
Describe the bug
I cannot PXE boot any hosts (UEFI or BIOS) using a new Cobbler install.
When I try to PXE boot with UEFI I just get No Media. When I try to boot from BIOS, I get a TFTP Error - File Not Found. The dhcpd.conf says the file should be either grub.0 or grubx64.efi. I can get either of those files using a manual tftp client.
Cobbler version
3.3.3
Operating system
Rocky Linux 9.1
So one of the problems is that the value for the tftp file name was not being inherited. I enabled verbose logging on the tftp server and saw this in the logs:
Sep 25 09:50:40 in.tftpd[5753]: RRQ from ::ffff:172.27.230.223 filename << inherit >> Sep 25 09:50:40 in.tftpd[5753]: Client ::ffff:172.27.230.223 File not found << inherit >>
I set the DHCP Filename Override and I was able to get further. I'm now able to successfully PXE boot using BIOS and the pxelinux.0 file. I still havent' gotten EFI to work.
-Brendan
After setting DHCP Filename Override to grub/grubx64.efi and having the correct grubx64.efi in that location, I was able to get EFI boot to work.
I also had to add the following kernel options to the distro: --kernel-options "inst.repo=http://172.27.230.204/cblr/distro_mirror/Rocky9-x86_64/BaseOS/ inst.addrepo=http://172.27.230.204/cblr/distro_mirror/Rocky9-x86_64/AppStream/ inst.stage2=http://172.27.230.204/cblr/distro_mirror/Rocky9-x86_64/"
-Brendan
@btsherid good day! I am kind of new with this, and I am having the same issue than you, I have tried what I believe you are proposing above, however I have not been successful so far, would it be possible you can provide more detail on the how and where you apply the 2 options for legacy and EFI.
Using rocky 9.2.
Thanks in advance.
@btsherid So the first bug you are describing is referencing #3161. It is fixed and a bugfix release will come out as soon as further testing has been done by me.
Furthermore, the second bug you are describing is probably related or identical to #3417. This will also be fixed with the previously mentioned bugfix release.
Am having similar problems - a detailed set of steps to 'workaround' to get this working would be SUPER helpful.
@pauliopolis For the first bug (#3161) there is not workaround except to patch the source code. For the second one (#3417) the workaround can be found in the issue itself.
@pauliopolis i had the same problem. My new Cobbler Server 3.3.3 is running on AlmaLinux 9.3 (EFI) and my new Server for the Automation installation is also a AlmaLinux 9.3 (EFI). I had to set the filename of my profile to /grub/grubx64.efi . before the filename in the dhcpd.conf was << inherit >>
@SchoolGuy i am right - that the bug fix in #3161 only removes the << inherit >> line from the dhcp.conf? but should it not normaly be filled with the right filename instead of removing the line? because tftpd will be failing with "file not found" or not?
@3XC1T3D If the filename
directive is missing that is correct since there should be another filename directive from the DHCP configuration that gives the hardware depending on its architecture the correct filename. As such a "file not found" could indicate either another bug or in incorrectly configured DHCP template.