Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
When radvd is configured to tell clients to use stateful configuration, EFI firmware obtains address straight away. But that might result in multiple adresses leased for PXE booting.
Discussed extensively as part of bug #1998448.
Version-Release number of selected component (if applicable):
edk2-ovmf-20200801stable-4.fc34.noarch
How reproducible:
reliable, not 100%
Steps to Reproduce:
1. enable AdvManagedFlag on; in radvd
2. try to boot using PXE
3.
Actual results:
Multiple leases are created.
Expected results:
Just single lease is used, InfoRequest might be used later to fetch more options.
Additional info:
Comment 1Klaus Heinrich Kiwi
2021-09-28 11:30:46 UTC
I'm assigning this to Gerd for further analysis / comments - doesn't mean a decision has been reached about our commitment to deliver it (patches always welcome)
Worth investigating. Doesn't look easy though.
The code collects offers, the goes pick the best. Not fully sure why,
maybe designed to work in networks where multiple dhcp servers are active
and not all of them responding with an offer usable for network boot.
Note that both UefiPxeBcDxe and HttpBootDxe are in the same boat, from
a quick grep it seems HttpBootDxe doesn't use InfoRequest too.
Comment 8Miroslav Rezanina
2022-09-05 07:09:30 UTC