Weird upgrade issue - vm pxe boots again and again after successful installation

Support
1

Dear foreman community,
I upgraded my old 1.12 foreman to 1.13, and then to 1.14 and then to 1.15.
Upgrade process worked well as documented and I am able to manage and
provision hosts with each upgrade.

However with the last upgrade from 1.14 to 1.15, I am able to provision the
host fine, but after final reboot, the vm PXE boots and starts installing
OS again.

I tried searching this forum but did not find any reference to the issue. I
saw some references to changing the boot order and modifying libvirt.rb but
my libvirt.rb has hd as the only option.

Any pointer/ assistance will be greatly appreciated.

Thanks,
Shri

2

check that you call the right built url within your install, that changed:

Greetings,
Klaas Demter

ATIX - The Linux & Open Source Company

----- Ursprüngliche Mail -----

··· Von: "Shrirang Alulkar" An: "Foreman users" Gesendet: Dienstag, 1. August 2017 22:23:08 Betreff: [foreman-users] weird upgrade issue - vm pxe boots again and again after successful installation

Dear foreman community,
I upgraded my old 1.12 foreman to 1.13, and then to 1.14 and then to 1.15.
Upgrade process worked well as documented and I am able to manage and
provision hosts with each upgrade.

However with the last upgrade from 1.14 to 1.15, I am able to provision the
host fine, but after final reboot, the vm PXE boots and starts installing
OS again.

I tried searching this forum but did not find any reference to the issue. I
saw some references to changing the boot order and modifying libvirt.rb but
my libvirt.rb has hd as the only option.

Any pointer/ assistance will be greatly appreciated.

Thanks,
Shri

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

3

Thanks Klass,
That was the problem. As a matter of fact the problem is well documented
here
(https://groups.google.com/forum/#!msg/foreman-users/IuvPJqeIpMM/g1Z2018WBAAJ)
To summarize the fix:
The kickstart template creates a KS file in /var/lib/tftpboot/pxelinux.cfg/
dir with the file name HEX IP (?) of the system being built.
Then once the KS process is complete the KS process has an API call to let
foreman know that it has finished building.

The default call is like this: wget -q -O /dev/null --no-check-certificate
<%= foreman_url %>
I changed it to : wget -q -O /dev/null
–no-check-certificate <%= foreman_url*('built')* %>

That fixed the issue. I am sure that the default 1.15 provisioning template
accounts for this but the upgrade does not.

The issue is resolved.

Cheers
Shri

··· On Wednesday, August 2, 2017 at 5:51:14 AM UTC-4, Klaas Demter wrote: > > check that you call the right built url within your install, that changed: > > https://github.com/theforeman/community-templates/blob/1.15-stable/provisioning_templates/provision/kickstart_rhel_default.erb#L171 > > Greetings, > Klaas Demter > > ATIX - The Linux & Open Source Company > > ----- Ursprüngliche Mail ----- > Von: "Shrirang Alulkar" <shrirang...@gmail.com > > An: "Foreman users" <forema...@googlegroups.com > > Gesendet: Dienstag, 1. August 2017 22:23:08 > Betreff: [foreman-users] weird upgrade issue - vm pxe boots again and > again after successful installation > > Dear foreman community, > I upgraded my old 1.12 foreman to 1.13, and then to 1.14 and then to 1.15. > Upgrade process worked well as documented and I am able to manage and > provision hosts with each upgrade. > > However with the last upgrade from 1.14 to 1.15, I am able to provision > the > host fine, but after final reboot, the vm PXE boots and starts installing > OS again. > > I tried searching this forum but did not find any reference to the issue. > I > saw some references to changing the boot order and modifying libvirt.rb > but > my libvirt.rb has hd as the only option. > > Any pointer/ assistance will be greatly appreciated. > > Thanks, > Shri > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-user...@googlegroups.com . > To post to this group, send email to forema...@googlegroups.com > . > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. >