From 1ea10ede18b4bacc2aca04fccb26c34976962ed7 Mon Sep 17 00:00:00 2001 From: huangxiangyu Date: Sat, 1 Apr 2017 17:06:54 +0800 Subject: Fix vlan network can't deploy instance JIRA: COMPASS-533 Bug: When a vlan network is created and bind to a physical network, the instances launched on this network will fail to get ip address from openstack dhcp server. Solution: Set enable_isolated_metadata to True in dhcp_agent.in Change-Id: I97cf8684d1ec9beeaa30e0ffa290150046ebcab1 Signed-off-by: huangxiangyu --- .../adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'deploy/adapters/ansible/roles/neutron-controller/templates') diff --git a/deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini b/deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini index 19eb62ec..4340c39c 100644 --- a/deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini +++ b/deploy/adapters/ansible/roles/neutron-controller/templates/dhcp_agent.ini @@ -40,7 +40,7 @@ use_namespaces = True # specific host routes to the DHCP request. The metadata service will only # be activated when the subnet does not contain any router port. The guest # instance must be configured to request host routes via DHCP (Option 121). -enable_isolated_metadata = False +enable_isolated_metadata = True # Allows for serving metadata requests coming from a dedicated metadata # access network whose cidr is 169.254.169.254/16 (or larger prefix), and -- cgit 1.2.3-korg