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:
From https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/provisioning_hosts/index?lb_target=preview , while following "5.2. Chainbooting iPXE from PXELinux" , The "ipxe.lkrn" method works great but not the undionly-ipxe.0.
The attempt to use undionly-ipxe.0 on a RHEL libvirt based VM fails with the error "Network Unreachable"
Version-Release number of selected component (if applicable):
satellite-6.13.0-6.el8sat.noarch
ipxe-bootimgs-x86-20181214-11.git133f4c47.el8.noarch
# md5sum /usr/share/ipxe/undionly.kpxe /var/lib/tftpboot/undionly-ipxe.0
f2c10b79c4c526bdc6d278f7fbe955c5 /usr/share/ipxe/undionly.kpxe
f2c10b79c4c526bdc6d278f7fbe955c5 /var/lib/tftpboot/undionly-ipxe.0
How reproducible:
Always
Steps to Reproduce:
1. Inside a RHEL Libvirt infra, install a Satellite 6.13
2. Configure all provisioning related resources i.e. content\services\subnet\domain etc.
3. Ensure to follow the Prerequisites properly from the said documentation and also configure the "--foreman-proxy-dhcp-ipxefilename" as mentioned at the end of "5.2. Chainbooting iPXE from PXELinux"
4. Associate "PXELinux chain iPXE UNDI" template with the OS ( using which the kickstart will happen )
5. Build a Baremetal VM on the same libvirt infra
6. Use it's mac to create a Baremetal Host entry in Satellite UI using the same OS ( as step 4 ) and submit it for the build while selecting the PXELoader as "iPXE Chain BIOS "
7. Power up the VM in the network and observe it's booting in the console.
Actual results:
** It fetches the undionly-ipxe.0 properly via tftp but then fails to load anything else.
** Also throws an error "Network Unreachable" and then continues in an iPXE boot loop.
( screenshot attached )
Expected results:
** It should either work properly on libvirt or if we have any specific circumstances\configuration to additionally maintain\perform, It needs to be properly documented in our Provisioning guide.
** If the said issue is expected due to some issues with the iPXE UNDI firmware\bootloader only, Perhaps we should obsolete this process [ or remove it from our scope of support ].
Additional info:
sosreport , runtime logs from satellite and a pcap file is attached
In the past, I had tested it on Sat 6.10 and 6.9 as well [ while it was RHEL 7 ( both satellite and my libvirt infra ) ], and then also it never worked. So I am guessing, Either I am missing something in my configuration or else There are very specific circumstances under which it will work.
It's best if we figure out what it is and then fix the docs as per the same.
The less confusing content we have in the Provisioning guide the better it would be.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.