From 52f37cdac0babd42eabab6b454a3f192127f9796 Mon Sep 17 00:00:00 2001 From: Mohammed Naser Date: Fri, 1 Feb 2019 17:42:38 -0500 Subject: [PATCH] nspawn: use mv-flat for host_bind_overrides If we don't use mv-flat, it will default to eth0 and when Neutron tries to bridge it, it will kill all connectivity to the VM. Change-Id: I74548b753ebccd63e47a567c15663b74a88c9333 --- etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 | 1 + 1 file changed, 1 insertion(+) diff --git a/etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 b/etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 index 18d0e190e5..1859223707 100644 --- a/etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 +++ b/etc/openstack_deploy/openstack_user_config.yml.aio-nspawn.j2 @@ -33,6 +33,7 @@ global_overrides: - network: container_bridge: "{{ ansible_default_ipv4['alias'] }}" container_interface: "mv-flat" + host_bind_override: "mv-flat" ip_from_q: "flat" type: "flat" net_name: "flat"