chainloading failed

[Oleg]

Server

• FOG Version: RC-13
• OS: Ubuntu 14.04.05

Client

• Service Version:
• OS: Ubuntu 14.04.04

Description

deploying image over the web-interface is running, registering the client is running and HDD boot is also running.
If I try to deploy image over the ipxe menu, i get the “chainloading failed”

http://192.168.94.111/fog/service/ipxe/boot.php... ok
Chainloading failed, hit 's' for the iPE shell: reboot in 10 seconds

if I choose “Quick Host Deletion” i get quiet the same (after confirm deletion with ‘y’)

http://192.168.94.111/fog/service/ipxe/boot.php... ok
Could not boot: Operation canceld (http://ipxe.org/0b22e0a0)
Could not boot: Operation canceld (http://ipxe.org/0b22e0a0)
Chainloading failed, hit 's' for the iPE shell: reboot in 10 seconds

How i remember in RC-5 everything worked fine. First time i got this issues was in RC-10. But the issue could be earlier.
The boot menu exit types are “SANBOOT” and EFI is "EXIT.

[Tom Elliott]

@Oleg anything in Apache error logs?

[Oleg]

no there is nothing in the apache error log.
If the client is not registered, it’s possible to chosse the direct deployment in the menu. Everything runs fine.
But if the client is already registered, then I get the error with the “chainloading failed”

[Sebastian Roth]

@Oleg Please open http://192.168.94.111/fog/service/ipxe/boot.php?mac=aa:bb:cc:dd:ee:ff (put the clients MAC here) in your browser and post the full output here.

[Oleg]

@Sebastian-Roth

#!ipxe
set fog-ip 192.168.94.111
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://192.168.94.111/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0x00567a 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is registered as 901b0e2dbdea!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.deployimage Deploy Image
item fog.quickdel Quick Host Deletion
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.94.111/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.quickdel
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param delhost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.94.111/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://192.168.94.111/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

[Wayne Workman]

I was able to reproduce the chainloading error when trying Image Deploy from the boot menu.

It only happens to me when an image is not assigned to the host. When an image is assigned, it works fine for me. I’ve made @Tom-Elliott aware.

I tested other stuff too though:

• Unregistered Image Deploy works still.
• Full registration with imaging works still.

[Tom Elliott]

@Wayne-Workman Found and fixed both of the underlying issues with this.

Sorry I made less DB calls but in doing that I made an err in logic checking.

[Wayne Workman]

Confirmed fixed in working-RC-14 Version 26, so it should be good in RC-14 when that is released.

[Sebastian Roth]

@Oleg Thanks again for reporting. Are you able to update to the latest version to see if this is fixed for you too?

[Oleg]

@Sebastian-Roth
not yet. the last version is still the RC-13. Will try if the new version is online. Thanks

[ch3i]

Bug solved in latest SVN, I had that bug before.