Foreman Discovery image and UEFI cannot get node to use boot interface to auto-continue

Robert_Anderson · April 11, 2017, 2:43pm

I am new to Foreman and am trying to use the Discovery plugin with Smart
Proxy. PXE boot to legacy BIOS works fine and auto-continues, gathers
facts and the node gets discovered. However, when shifting to UEFI boot
mode and booting to the Foreman Discovery image using the same kernel
parameters I get halted at the Manual/PXE-less provisioning workflow
screen. At this point the image requires manual intervention to select
Manual network setup or Discover with DHCP. I would like the image to
continue automatically using the boot interface that it DHCPed with as it
did with when booting with Legacy BIOS. Any suggestions to accomplish this
with UEFI?

I am using fdi v3.3.1 (20170104.1)

lzap · April 12, 2017, 8:51am

Hey Robert,

welcome to the Foreman community!

So I assume you are using PXEGrub2 (default) template to PXE-boot
discovery. We have this default template snippet:

github.com

theforeman/community-templates/blob/develop/provisioning_templates/snippet/pxegrub2_discovery.erb

<%#
kind: snippet
name: pxegrub2_discovery
model: ProvisioningTemplate
snippet: true
-%>
<%#
RHEL 7 virtio driver does not have persistent naming scheme, causing interfaces
to be named eth0, eth1, etc.. If you want to enable the new persistent naming
scheme and get inteface names like ens3, add net.ifnames=1 to the linuxefi line
below. This will not be fixed until RHEL8 due to prevent breaking changes for
existing systems. See RHBZ#1259015 for more details.

Another bug in RHEL 7.4 is affecting $net_default_mac with a trailing slash, in
the global template we have a regexp module creating corrected variable $mac
which is used here. See RHBZ#1487107 for more info.
-%>
menuentry 'Foreman Discovery Image' {
  linuxefi boot/fdi-image/vmlinuz0 rootflags=loop root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset proxy.url=<%= foreman_server_url %> proxy.type=foreman BOOTIF=01-$mac
  initrdefi boot/fdi-image/initrd0.img

This file has been truncated. show original

can you pastebin your configuration file you have on your TFTP server?

The most important parameter is BOOTIF, if that's present FDI knows
this was PXE-booted and starts. If that's missing then PXE-less mode
is entered (manual mode). Make sure you have this option.

LZ

···

On Tue, Apr 11, 2017 at 4:43 PM, Robert Anderson wrote: > I am new to Foreman and am trying to use the Discovery plugin with Smart > Proxy. PXE boot to legacy BIOS works fine and auto-continues, gathers facts > and the node gets discovered. However, when shifting to UEFI boot mode and > booting to the Foreman Discovery image using the same kernel parameters I > get halted at the Manual/PXE-less provisioning workflow screen. At this > point the image requires manual intervention to select Manual network setup > or Discover with DHCP. I would like the image to continue automatically > using the boot interface that it DHCPed with as it did with when booting > with Legacy BIOS. Any suggestions to accomplish this with UEFI? > > I am using fdi v3.3.1 (20170104.1) > > -- > 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.

–
Later,
Lukas @lzap Zapletal

Robert_Anderson · May 30, 2017, 9:18pm

Lukas,

Sorry I didn't see this sooner. Wow, totally missed that var in the
template. That was it. That did the trick. Thank you.

···

On Wednesday, April 12, 2017 at 4:51:51 AM UTC-4, Lukas Zapletal wrote: > > Hey Robert, > > welcome to the Foreman community! > > So I assume you are using PXEGrub2 (default) template to PXE-boot > discovery. We have this default template snippet: > > > https://github.com/theforeman/community-templates/blob/develop/provisioning_templates/snippet/pxegrub2_discovery.erb > > can you pastebin your configuration file you have on your TFTP server? > > The most important parameter is BOOTIF, if that's present FDI knows > this was PXE-booted and starts. If that's missing then PXE-less mode > is entered (manual mode). Make sure you have this option. > > LZ > > On Tue, Apr 11, 2017 at 4:43 PM, Robert Anderson > wrote: > > I am new to Foreman and am trying to use the Discovery plugin with Smart > > Proxy. PXE boot to legacy BIOS works fine and auto-continues, gathers > facts > > and the node gets discovered. However, when shifting to UEFI boot mode > and > > booting to the Foreman Discovery image using the same kernel parameters > I > > get halted at the Manual/PXE-less provisioning workflow screen. At this > > point the image requires manual intervention to select Manual network > setup > > or Discover with DHCP. I would like the image to continue automatically > > using the boot interface that it DHCPed with as it did with when booting > > with Legacy BIOS. Any suggestions to accomplish this with UEFI? > > > > I am using fdi v3.3.1 (20170104.1) > > > > -- > > 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. > > > > -- > Later, > Lukas @lzap Zapletal >