Bug 1443139
| Summary: | dhcp-vendorclass doesn't match in dhcpv6 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Derek Higgins <derekh> |
| Component: | dnsmasq | Assignee: | Petr Menšík <pemensik> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Ščotka <jscotka> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | pemensik, psklenar, racedoro, thozza |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | dnsmasq-2.76-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 22:56:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1335964 | ||
|
Description
Derek Higgins
2017-04-18 14:57:12 UTC
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 |