Problem:
Pxe install impossible after upgrade foreman 3.13.0 to 3.14.0
Expected outcome:
installing new host which foreman’s pxe boot
Foreman and Proxy versions:
3.14.0
Distribution and version:
rocky linux 9.5
i have a theforeman 3.13.0 running which works like charm.
The OS is rocky linux 9.5
The upgrade to Version 3.14.0 makes problems with pxe boot install (managing the hosts by puppet still works on 3.14.0)
The problem with pxe: When i try to install a computer over pxe boot, the new host contacts the theforeman server, and also gets an IP address from the dhcp server (which is identical with the theforeman server). So far, so expected.
But then it hangs and the new host falls back into the BIOS.
This is the way how i upgraded theforeman from 3.13.0 to 3.14.0:
yum update
reboot
cd /etc/yum.repos.d/
sed -i -e ‘s/3.13/3.14/g’ foreman.repo
sed -i -e ‘s/3.13/3.14/g’ foreman-plugins.repo
cd /etc/pki/rpm-gpg/
rm RPM-GPG-KEY-foreman
wget https://yum.theforeman.org/releases/3.14/RPM-GPG-KEY-foreman
yum update
foreman-rake db:migrate
reboot
Hi,
Does it mean that the host is getting the configuration files for the bootloader from the Foreman, and the error happens after you select one of the options in the bootloader menu?
yes, exactly.
The server on which theforeman is installed also hosts theforeman-proxy, tftp and dhcp
When i select on the boot loader menu of the host where i want to install the OS the pxe boot, it gets a valid IP address from theforeman server (or better: it’s DHCP server) and then falls back to the boot loader menu.
It seems it cannot download the boot image after the upgrade to 3.14.0 what went without problems before the upgrade on 3.13.0.
Hi,
now i have to apologize that i did not give you guys all the informations. Lesson lerned. I was too much blinded by “before the upgrade it worked”.
The root cause of my problem was that i have two interfaces, but pxe boot works only on one. The install host took the IP address from theforeman’s other interface, and so the image could not be downloaded and the pxe fell back into the boot menu.
I fixed is by giving foreman-proxy-tftp-servername to the foreman-installer.
Here is now my way to the upgrade from 3.13 to 3.14 (i have private network addresses, replace it by your’s):
yum update
systemctl stop foreman
cd /etc/yum.repos.d/
sed -i -e ‘s/3.13/3.14/g’ foreman.repo
sed -i -e ‘s/3.13/3.14/g’ foreman-plugins.repo
cd /etc/pki/rpm-gpg/
rm RPM-GPG-KEY-foreman
wget https://yum.theforeman.org/releases/3.14/RPM-GPG-KEY-foreman
yum update
foreman-rake db:migrate
reboot
