Description of problem:

For azure custom image-based provisioning, the Kickstart default template is being rendered, which is not required. Because of this, it asks for missing Media, Partition Table, and Content Source — all of which are not needed for custom image provisioning. As a result, the provisioning itself works, but the build status remains stuck at Pending installation instead of switching to Build. This issue does not occur in 6.17, where the Kickstart default template is not rendered. I am also sharing the error message and screenshots of both cases.
 

2025-09-30T08:34:31 [W|app|fa4ee26b] Could not find a provider for garry-drube.ppdj2hf3be. Providers returned {"MediumProviders::Default"=>["RedHat 9.6 medium was not set for host 'garry-drube.ppdj2hf3be'", "Invalid medium '' for 'RedHat 9.6'"], "Katello::ManagedContentMediumProvider"=>["Kickstart repository was not set for host 'garry-drube.ppdj2hf3be'", "Content source was not set for host 'garry-drube.ppdj2hf3be'"]}
2025-09-30T08:34:31 [W|app|fa4ee26b] Error while rendering 'Kickstart default' template
2025-09-30T08:34:31 [I|app|fa4ee26b] Backtrace for 'Error while rendering 'Kickstart default' template' error (Foreman::Exception): ERF42-6371 [Foreman::Exception]: Neither disk nor partition table defined for host

How reproducible:

Always

Is this issue a regression from an earlier version:

Yes

Steps to Reproduce:

1. Create azure compute-resource https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html/provisioning_hosts/provisioning_cloud_instances_on_microsoft_azure_resource_manager_azure-provisioning#Adding_a_Microsoft_Azure_Resource_Manager_Connection_azure-provisioning

and custom image in it. custom://imageVM1-RHEL7-image-20220617150105
https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html/provisioning_hosts/provisioning_cloud_instances_on_microsoft_azure_resource_manager_azure-provisioning#adding-images-to-server_azure-provisioning

2. Create a host with azure.
https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html/provisioning_hosts/provisioning_cloud_instances_on_microsoft_azure_resource_manager_azure-provisioning#creating-image-only-hosts_azure-provisioning

Actual behavior:
Due to unnecessary template rendering, the status remains stuck at Pending Installation during custom image provisioning.

Expected behavior:
After custom image-based provisioning, the build status should be set to Installed.