Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionHradayesh Shukla
2018-03-23 17:24:45 UTC
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.
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