Feature #17297
closed
GRUB 2 PXE loader entries for Debian OS family
Description
I installed foreman 1.13.1 and completed the setup. Since we have machines to be booted with UEFI, I was looking forward to use the announced UEFI features. However, when adding a new host, there is no selectable entry for "PXEGrub2 UEFI" as advertised in the manual. In fact, there is also no provisioning template with a hint for UEFI (and I don't know whether there should be one).
However, since I only use the TFTP smart proxy, I configured our DHCP server to provide grub2/grubx64.efi and the server also seems to load it. Anyways, this does not succeed since it results in showing a completely black screen and eventually the machine reboots. Therefore, I think I am missing some features or I did configure the build wrongly.
Updated by Dominic Cleal about 8 years ago
- Priority changed from Urgent to Normal
Which architecture and OS are you booting? It looks as though the boot loader selection is restricted by OS.
For support queries, please prefer the mailing list and IRC channel: https://theforeman.org/support.html. The issue tracker has very limited visibility.
Updated by Sebastian Dreßler about 8 years ago
Dominic Cleal wrote:
Which architecture and OS are you booting?
x86_64 and Ubuntu (which is Debian internally as it seems).
For support queries, please prefer the mailing list and IRC channel: https://theforeman.org/support.html. The issue tracker has very limited visibility.
Thanks for the hint.
Updated by Dominic Cleal about 8 years ago
- Tracker changed from Support to Feature
- Subject changed from Cannot see PXE load entries for UEFI to GRUB 2 PXE loader entries for Debian OS family
OK, then it's missing for Debian. I don't see any reason it should be, particularly because the necessary boot files are configured by the installer.
I've changed this ticket from support to track this change instead.
Updated by Dominic Cleal about 8 years ago
- Related to Feature #12634: New HW Model flag pxe_loader in UI/API added
Updated by Lukas Zapletal about 8 years ago
Hi, you don't see these loaders because you don't have PXEGrub or PXEGrub2 templates associated with your OS. You need to create and associate them.
We currently do not ship any Debian/Ubuntu templates, they needs to be created (similarly to Red Hat which is here for example https://github.com/theforeman/community-templates/blob/develop/kickstart/PXEGrub2.erb). It's an easy task, but I did not have time to test these yet.
I don't think this is a bug in core, but rather RFE in Templates category.
Updated by Dominic Cleal about 8 years ago
Lukas Zapletal wrote:
Hi, you don't see these loaders because you don't have PXEGrub or PXEGrub2 templates associated with your OS. You need to create and associate them.
Isn't the list of PXE loaders populated from os.available_loaders?
The implementation on Operatingsystem itself is just ["None", "PXELinux BIOS"] but the Redhat subclass adds GRUB 2 etc. Some of the other OS families have it overridden to "None" only. The Debian family has no override, so it only has the None/PXELinux BIOS defaults.
Updated by The Foreman Bot about 8 years ago
- Status changed from New to Ready For Testing
- Assignee set to Lukas Zapletal
- Pull request https://github.com/theforeman/foreman/pull/4015 added
Updated by Lukas Zapletal about 8 years ago
You're right. I have sent a patch. During the long review, I had changed it to be more explicit. Sorry for confusion.
Updated by Lukas Zapletal about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset b3659e87a1727b4fab616e6060ff55969b76ab56.
Updated by Dominic Cleal about 8 years ago
- Translation missing: en.field_release set to 203
Updated by