+++ This bug was initially created as a clone of Bug #1122152 +++ Foreman: The "LOCALBOOT 0" entry causes some bare metal machines to stuck during boot. Environment: rhel-osp-installer-0.1.1-1.el6ost.noarch foreman-proxy-1.6.0.8-1.el6sat.noarch foreman-installer-1.5.0-0.4.RC2.el6ost.noarch ruby193-rubygem-foreman-tasks-0.6.4-2.el6sat.noarch rubygem-foreman_api-0.1.11-4.el6sat.noarch openstack-foreman-installer-2.0.15-1.el6ost.noarch foreman-discovery-image-6.5-20140620.2.el6sat.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch openstack-puppet-modules-2014.1-19.1.el6ost.noarch Description: The PXE file created for VMs with intention to boot from the HD (here: /var/lib/tftpboot/pxelinux.cfg/<MAC>) contains the following: DEFAULT menu PROMPT 0 MENU TITLE PXE Menu TIMEOUT 200 TOTALTIMEOUT 6000 ONTIMEOUT local LABEL local MENU LABEL (local) MENU DEFAULT LOCALBOOT 0 Result: Some HW (for example Dell PowerEdge C6100) isn't able to boot the OS from the HD when this option is selected after booting via PXE. Expected result: All machines should be able to boot from the HD, when selecting the "local" option after booting via PXE. Note: the following workaround found to be working on all machines (so far): label local MENU LABEL (local) MENU DEFAULT COM32 chain.c32 APPEND hd0 0
Created redmine issue http://projects.theforeman.org/issues/6725 from this bug
Facing the same issues when deploying OS on bare metal Dell machines.
Facing the same issue with a bare metal System X (x3850 X5 - 7143).
I can confirm that this is an issue with RHEL OSPI v6 (Juno) as well.
Upstream bug component is Provisioning Templates
This bug is being tracked upstream, and will no longer be tracked in the downstream product. When the upstream issue is fixed, the next Satellite release will contain the fix. I am closing this out as deferred. If you feel this is not correct, please feel free to open with additional information.