No validation for DHCP options may lead to potential issues with different dhcp backends
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
DHCP option names are not standardized and option names that works with dnsmasq doesn't work with Contrail. By trying to switch to dhcp option values we found that it breaks dnsmasq case. As dnsmasq always set `siaddr` field in dhcp reply to dnsmasq host ip unless `server-ip-address` is not configured. This field is treated by pxe client as tftp server more information about this may be found here https:/
We left this dnsmasq internal option `server-
Changed in neutron: | |
importance: | Undecided → Wishlist |
tags: | added: l3-ipam-dhcp |
If someone has the time to work on this, seems like maybe it could come through the blueprint/spec process, just to make sure everyone is on the same page.
[1] https:/ /docs.openstack .org/neutron/ latest/ contributor/ policies/ blueprints. html