Description of problem: Foreman discovery image 3.4.4-1 doesn't boot with UEFI for VM (hyper-v gen2 ) Version-Release number of selected component (if applicable): foreman-discovery-image-3.4.4-1.iso How reproducible: Steps to Reproduce: 1. Boot the VM in UEFI with the foreman-discovery-image-3.4.4-1.iso 2. When booting with the foreman-discovery-image provided with the Red Hat Satellite, booting fails with error: Unable to load the kernel. 3. If you try to access the shell, it hangs and you have to start the provisioning again from scratch. 4. If you use the upstream (community) FDI ISO, it boots properly and provisioning is successful. Actual results: - When booting with the foreman-discovery-image provided with the Red Hat Satellite, booting fails with error: Unable to load the kernel. -If you try to access the shell, it hangs and you have to start the provisioning again from scratch. Expected results: - Should boot like the community FDI and result in successful provisioning Additional info:
Satellite 6 FDI builds won't work for locally mounted ISO (PXE-less workflow) because Hyper-V SCSI is not present on the initramdisk. Symptoms are one minute delay and then: /dev/disk/by-label/foreman-discovery-image-3.x.x-x does not exist Keyboard does not work, because keyboard driver is not present as well. This was fixed upstream in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1192030 I created backport request into RHEL7: https://bugzilla.redhat.com/show_bug.cgi?id=1595574 Once this is fixed, we need to make sure the livecd-tools in our brew buildroot contains the patch, then we can rebuild the FDI.
Lowering priority, discovery is supported only on bare metal, this is a VM - best effort. We need to do some buildroot changes in order to fix this.
Created tracker for this bug, moving to NEW since we need to patch livecd-creator first and then we can build.
This must be backported into FDI in Sat 6.3 AND 6.4, it is gonna be KS change.
*** Bug 1595574 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2928