-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.18.0
Description of problem:
Host details page shows incorrect PXE loader for host provisioned on VMware, and we found this issue while testing the fix for https://issues.redhat.com/browse/SAT-30594
How reproducible:
Always
Is this issue a regression from an earlier version:
No
Steps to Reproduce:
1. Prepare Satellite 6.18.0/stream for Provisioning, and create a VMware CR with image
2. Create a host group with PXE Loader like "PXELinux BIOS" or add this while host creation in next step.
3. Create a host to deploy on VMware CR, choose any firmware like UEFI/UEFI Secureboot which is other than PXE loader set
4. Verify host is deployed successfully with UEFI firmware and validate Host details page for PXE loader
Actual behavior:
Host details page shows incorrect PXE loader for host provisioned from Image on VMware, like it here it shows "PXELinux BIOS"
Expected behavior:
Host details page shows correct PXE loader or matches to firmware opted for host provisioned from Image on VMware, like it here it should show either "Grub2 UEFI" or "Grub2 UEFI Secureboot"
Business Impact / Additional info:
- relates to
-
SAT-30594 Virtual TPM option doesn't work with Image based provisioning method
-
- Release Pending
-