c7f572d65b
If enable_dhcp is set on subnet, but, for some reason neutron did not have any DHCP port yet, we still want the network_info to be populated with a valid dhcp_server value. This is mostly useful for the metadata API (which is relying on this value to give network_data to the instance). This will also help some providers which are using external DHCP servers not handled by neutron. In this case, neutron will never create any DHCP port in the subnet. Also note that we cannot set the value to None because then the value would be discarded by the metadata API. So the subnet gateway will be used as fallback. Change-Id: Ie2cd54c159ea693e48e00d0ca3b0ca5a468d79cb Signed-off-by: Arnaud Morin <arnaud.morin@corp.ovh.com>
6 lines
207 B
YAML
6 lines
207 B
YAML
---
|
|
features:
|
|
- When ``enable_dhcp`` is set on a subnet but there is no DHCP port on neutron
|
|
then the ``dhcp_server`` value in meta hash will contain the subnet
|
|
gateway IP instead of being absent.
|