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.
Description of problem:
The foreman-discovery images 3.5.4-8 and 3.6.7-1 (provided with the Red Hat Satellite 6.8.1-1) do not boot on HyperV 2016 VM.
Version-Release number of selected component (if applicable):
- foreman-discovery-image-3.5.4-8.iso
- foreman-discovery-image-3.6.7-1.iso
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 6.8.1-1, booting fails with error:
~~~
dracut-initqueue[474]: Warning: dracut-initqueue timeout - starting timeout scripts
dracut-initqueue[474]: Warning: Could not boot.
dracut-initqueue[474]: Warning: /dev/disk/by-label/fdi does not exist
dracut-initqueue[474]: Warning: /dev/mapper/live-rw does not exist
~~~
Expected results:
- Should boot like the community FDI and result in successful provisioning.
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 (Moderate: Satellite 6.9 Release), 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/RHSA-2021:1313