Introduction:
This document explains the meaning of Satellite Error – PXE Boot Loop and some instructions to fix it.
This satellite PXE Boot Loop error is relevant in case you trying to build a new machine from satellite and the pxe boot is stack.
The meaning of the error is that a user is trying to build a new host and the “Kickstart default PXELinux” message display with seconds that decreased and the “Automatic boot in X seconds…” message displayed again and again.
This error is caused when a repo is not availably for some reason and someone is trying to build a machine. In this case, the boot files vmlinuz & initrd.img is corrupted.
These files are key components of the linux boot process
[root@satellite boot]# cd /var/lib/tftpboot/grub2/boot
[root@satellite boot]# ls -la
-rw-r–r–. 1 foreman-proxy foreman-proxy 94 Mar 24 11:03 red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-10-3087-initrd.img
-rw-r–r–. 1 foreman-proxy foreman-proxy 94 Mar 24 11:03 red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-10-3087-vmlinuz
You can see that the files is corrupted:
[root@satellite boot]# cat red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-10-3087-vmlinuz
404: Distribution is not pointing to a publication, repository, repository version, or remote.
All you need to do is to delete the corrupted files and they will generated again.
After it you can cancel build and build the machine again
Summary:
This guide provides step-by-step instructions for fixing “PXE Boot Loop” error in satellite.
Here you can see another satellite error and some actions to fix it.
