Description of problem: When host specific image is downloaded from the Satellite server, it always takes default bootdisk template settings instead of custom one assigned to operating system. Version-Release number of selected component (if applicable): Satellite 6.2 How reproducible: Always Steps to Reproduce: 1.Associate custom Bootdisk template to any Operating System. 2.Create a new Bare Metal profile. 3.Download the host specific image : Satellite UI -> Hosts -> All Hosts -> select the newly created host -> Click on 'Boot disk' button -> Download Host image Actual results: System tries to boot with the default bootdisk template. Expected results: It should boot using custom bootdisk template. Additional info: Workarounds: 1. Unlock the default bootdisk template and make changes to it. OR 1. https://github.com/theforeman/foreman_bootdisk ~~~ Customising boot disk templates The templates used on the boot disks themselves are read-only so they can be updated in new versions of the plugin. To customise, copy the contents to a new template and set the name in Administer>Settings>Bootdisk. ~~~
This is by the design, bootdisk only supports one generic iPXE template. Full Host disk supports PXELinux template associated with the OS tho, since it's not iPXE based but it uses SYSLINUX.
To elaborate, bootdisk uses PXELinux or iPXE template that is generic and can be cloned and set in Administer - Setting. That's only used for generation of the bootdisk itself. For iPXE based template it then chainloads template which is associated with the host (iPXE Template) which can be customized as needed (per host). For Full Host bootdisk tho, Anaconda loads directly so there is no intermediate iPXE template at all.