New iPXE Entries Not Showing

[Zer0Cool]

@quazz Yep noted here:

@zer0cool said in New iPXE Entries Not Showing:

@wayne-workman Is that the “Menu Show With”? I have it set to all hosts, I would presume that includes non-registered but there is an entry specifically for not registered.

Also here is the snippet from boot.php:

:os.Centos7
kernel tftp://${fog-ip}/centos7/images/vmlinuz
initrd tftp://${fog-ip}/centos7/images/initrd.img
imgargs vmlinuz initrd=initrd.img root=live:nfs://${fog-ip}/images/centos7/LiveOS/squashfs.img ip=dhcp
repo=nfs://${fog-ip}/images/centos7 splash quiet
boot || goto MENU
param sysuuid ${uuid}

I dont see anything out of place with it

Sorry, think this is what you meant:

:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
item os.Centos7
item test.menu
choose --default fog.local --timeout 120000 target && goto ${target}

Looks like both the entries I created are listed there (os.Centos7 and test.menu)

[Quazz]

@zer0cool Not what I mean. In Boot.php there is a :MENU entry that will have a structure like so:

:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)

If your entry isn’t part of the :MENU then it will never show in PXE boot.

[Zer0Cool]

@quazz Just relized that, edited prior reply with it

[Zer0Cool]

@quazz Ok wait a second, just noticed neither of my menus kept the description which I assume is the visible part i nthe menu, ie:

item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
item os.Centos7
item test.menu

My Centos7 and test entries have nothing to the right of them, which I assume comes from the description field…I did fill those in but now they are empty

[Quazz]

@zer0cool Are they still filled in on the FOG server?

[Zer0Cool]

@quazz Nope, this was the issue…

When I created the entries new, I did put in a description and saved them, the saved entry did not keep the description field, thus it was empty and the menu items were in the PXE boot menu, but blank under everything else (invisible).

I went back to the entry and gave it a description again via the “iPXE menu item settings” category and clicking o nthe menu entry and adding a description to the description field, then re-saving it. Checked and now shows in the PXE boot menu on the host.

Possible I made this mistake 2x…I guess but unlikely considering I recall deciding what I would make the description.

[george1421]

When I created the entries new, I did put in a description and saved them, the saved entry did not keep the description field, thus it was empty and the menu items were in the PXE boot menu, but blank under everything else (invisible).

@Developers you might want to take a peek at the code to confirm that on an edit of a fog ipxe menu that the updates are being saved back to the database.

[Tom Elliott]

@george1421 editing works it sounds like when saving a new item it’s not?

[Zer0Cool]

@tom-elliott This is accurate for me. When creating a new entry description doesnt save but the rest does. I am then able to edit it and add description.

I will be blowing out the server and rebuilding from the ground up in the near future as this was just testing, so I can revisit it then and confirm if it was an issue with my specific setup or a repeatable issue.

[Tom Elliott]

@zer0cool no need it’s easy enough to replicate I think and I can get it fixed pretty quick.

[Tom Elliott]

Fixed in working branch.