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:
In order to set a tag on dhcp PXE requests (and send appropriate bootfile values) in the dnsmasq config file I have
dhcp-vendorclass=set:pxe6,enterprise:343,PXEClient
the tag doesn't get set when the dhcp6 solicit packet comes in
Version-Release number of selected component (if applicable):
dnsmasq-2.66-21.el7.x86_64
How reproducible:
Every time
In order for the tag to be set we need a fix
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=ef1d7425e31df52f6d9c1427516ed55a0f8513ff
Giving a bit more context here, in order for network boot to work using dnsmasq as configured by openstack on Directors undercloud, I've had to set aside separate IP ranges for PXE, iPXE and deployed IP allocations of overcloud nodes.
This is being configured, by setting tags if PXE or iPXE is detected
dhcp-vendorclass=set:pxe6,enterprise:343,PXEClient
dhcp-userclass=set:ipxe6,iPXE
dhcp-range=tag:pxe6,fd00:1101::0001:0000:0000,fd00:1101::0001:ffff:ffff
dhcp-range=tag:ipxe6,fd00:1101::0002:0000:0000,fd00:1101::0002:ffff:ffff
dhcp-option=tag:pxe6,option6:bootfile-url,tftp://[fd00:1101::1]/ipxe.efi
dhcp-option=tag:ipxe6,option6:bootfile-url,http://[fd00:1101::1]:8088/boot.ipxe
but the first option "dhcp-vendorclass" doesn't work on RHEL 7.3's version of dnsmasq.
Hello Derek,
thank you for you report. Specified commit is already included in rebased version 2.76, already prepared for RHEL 7.4. It will be fixed in next minor release.
Hope that helps
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-2017:2117