Bug 1435381

Summary:	[Satellite 6.2]Host specific image doesn't honor custom bootdisk template settings.
Product:	Red Hat Satellite	Reporter:	Amar Huchchanavar <ahuchcha>
Component:	Bootdisk Plugin	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.8	CC:	bbuckingham, inecas, jcallaha, lzap, rbeyel
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-07 08:17:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Amar Huchchanavar 2017-03-23 16:28:58 UTC

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.
~~~

Comment 3 Lukas Zapletal 2017-11-07 08:17:22 UTC

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.

Comment 5 Lukas Zapletal 2019-11-22 13:33:47 UTC

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.