cobbler get-loaders fails on Centos 7 new install #2660
Comments
|
This seems pretty new; I installed cobbler on centos 7 a few weeks ago and did not encounter it. |
|
We removed the |
nodeg
added
the
Deprecated
|
@AlbertBraden The bootloaders of our website should have never been used in the first place. They were not updated for years and since I cannot guarantee for the content of it, I have taken them down. As said in other discussions and issues, I am expecting people to get them for themselves from the distros for numerous reasons. I am very sorry but updating, signing, as well es publishing the bootloaders is a task for more then a whole team, thus we cannot take care of this, even if it makes your life more complicated. |
|
Is there a document that explains how to manually update the bootloaders? |
|
@AlbertBraden They should be by the distro you want to install at least. And then you can use the normal workflows of Cobbler. |
|
After googling around it appeared that I needed syslinux.efi so I did this: mkdir -p /usr/local/src/loaders/ Then I edited dhcp.template and changed the filename to syslinux.efi, and ran cobbler sync, but the pxe-boot is hanging:
What am I doing wrong? |
|
If I remember correctly version 6.0.3 has a bug. For efi, you should be using grub. |
|
I searched on my Cobbler host and found /var/www/cobbler/ks_mirror/centos7-minimal-1908-x86_64/EFI/BOOT/grubx64.efi so I copied that into /var/lib/tftpboot/ along with grub.cfg, and changed the filename in dhcp.template, and that gives me a nice menu:
But it fails when I select an option:
What am I missing? |
|
@AlbertBraden Exactly what it tells you: It can't find the kernel where it expectes the kernel to be. That can either be due to a misconfiguration, a missing |
|
Until recently, I would install cobbler and run get-loaders and it would just work. Now that running get-loaders has been replaced with a complex and difficult process that is new to Cobbler users, can we get a document to help us download and install the correct loader and menu? |
|
@AlbertBraden Yes you may. Actually the (easy) process is already documented: https://cobbler.readthedocs.io/en/latest/quickstart-guide.html#importing-your-first-distribution The more complex/advanced one is distributed over the whole docs but I am working on improving the docs... |
|
Keep in mind that this is for the master branch and it might not work always. For the 2.8.5 release you may have a look here: https://cobbler.readthedocs.io/en/release28/3_general/cobbler%20direct%20command.html#import |
|
I read those two documents and I see the discussion about importing, but importing the distribution is a separate step from setting up the loader and menu, and I'm not seeing the loader/menu steps in there. I ended up spending most of the day experimenting with grub.cfg, and I ended up with this: This works for pxe-booting, but I am seeing a bunch of errors in /var/log/messages on the cobbler server. Do I still have something misconfigured? |
|
@AlbertBraden Yes these files are normally there if Cobbler is the one generating the TFTP directory and the The script is not deployed with Cobbler 2.8.5 but works perfectly well with it since it is independent of Cobbler. Just grab it from the |
|
@dansou901 @hbokh Please help me out here if you have a bit of time. Maybe I am seeing this from the wrong standpoint, you have more experience as users as I have... |
|
Interesting! This is going to bite us too in time, on our now +1 year old Cobbler 3.1.2 on Debian Buster (not CentOS7). FWIW, we have these loaders in On my even older Cobbler 3.1.2 at $HOME, running This might come in handy for @AlbertBraden to at least get some loaders in the right place. In the mean time I'm having a hard time setting up Cobbler 2.8.5 on CentOS7 in a VM again. |
|
This is a completely terrible experience for cobbler operators, and the timing is particularly bad as we are scrambling to build Centos 7 dev environments to test the migration to Centos 8, and then from Centos 8 to something else before the end of the year. If you could just make 2.8.5 work for a few more months (without the operator spending many hours hacking loaders and menus), that would be a huge service to the operators who are using your product. |
|
Some network boot-loaders are missing from /var/lib/cobbler/loaders, you may run 'cobbler get-loaders' to download them, or, if you only want to handle x86/x86_64 netbooting, you may ensure that you have installed a recent version of the syslinux package installed and can ignore this message entirely. Files in this directory, should you want to support all architectures, should include pxelinux.0, menu.c32, elilo.efi, and yaboot. The 'cobbler get-loaders' command is the easiest way to resolve these requirements. I wonder if anyone still needs |
|
Yes, UEFI is the issue, but UEFI works "out of the box" after running get-loaders. Without get-loaders it is a mess. |
|
I created an "archive" with the old loader files. I hope this can clean up your mess a bit. |
|
@opoplawski Could you create a patch which removes |
|
Done in 3.2.2-5 (Fedora, EPEL8, copr orion/cobbler) and 2.8.5-2 (EPEL7). |
|
This will not be fixed and the reasons are outlined in detail here. No activity for a while. Closing issue. |
Describe the bug
cobbler get-loaders fails with 404 error on Centos 7 new install
Steps to reproduce
Expected behavior
get-loaders completes successfully
Cobbler version
Operating system
CentOS Linux release 7.9.2009 (Core)
Cobbler log
Screenshots
Additional information
It looks like https://cobbler.github.io/loaders/COPYING.elilo doesn't exist.
The text was updated successfully, but these errors were encountered: