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 <huangxiangyu5@huawei.com>

diff --git a/deploy/adapters/ansible/roles/neutron-compute/templates/dhcp_agent.ini b/deploy/adapters/ansible/roles/neutron-compute/templates/dhcp_agent.ini
index 19eb62e..4340c39 100644 (file)
--- a/deploy/adapters/ansible/roles/neutron-compute/templates/dhcp_agent.ini
+++ b/deploy/adapters/ansible/roles/neutron-compute/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

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 19eb62e..4340c39 100644 (file)
--- 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

diff --git a/deploy/adapters/ansible/roles/neutron-network/templates/dhcp_agent.ini b/deploy/adapters/ansible/roles/neutron-network/templates/dhcp_agent.ini
index 19eb62e..4340c39 100644 (file)
--- a/deploy/adapters/ansible/roles/neutron-network/templates/dhcp_agent.ini
+++ b/deploy/adapters/ansible/roles/neutron-network/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

diff --git a/deploy/adapters/ansible/roles/nova-controller/templates/dhcp_agent.ini b/deploy/adapters/ansible/roles/nova-controller/templates/dhcp_agent.ini
index 19eb62e..4340c39 100644 (file)
--- a/deploy/adapters/ansible/roles/nova-controller/templates/dhcp_agent.ini
+++ b/deploy/adapters/ansible/roles/nova-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