From 749babc4c7a8a438ed24eaff9829ca96927a0ccb Mon Sep 17 00:00:00 2001 From: Monty Taylor Date: Sun, 10 Apr 2016 13:14:18 -0500 Subject: [PATCH] Tell os-client-config that tripleo doesn't have neutron The TripleO cloud does not work when the neutron-based floating ip logic creates a floating ip directly on a server port. The problem is that the floating IP is correctly created and correctly associated with the server, but Nova has no clue that this has happened, so GET calls to /server do not show that the server has the floating IP. As that's the way we track success, we can't use it. However, if a floating IP is created using the nova proxy, it all works - so just configure the cloud with "has_network: False" so that direct neutron interactions are not attempted. Change-Id: Idb90cad36feb99bc5aa19da4874ce97f868681c7 --- modules/openstack_project/templates/nodepool/clouds.yaml.erb | 1 + 1 file changed, 1 insertion(+) diff --git a/modules/openstack_project/templates/nodepool/clouds.yaml.erb b/modules/openstack_project/templates/nodepool/clouds.yaml.erb index 9f7d4e1cfe..1835e8c856 100644 --- a/modules/openstack_project/templates/nodepool/clouds.yaml.erb +++ b/modules/openstack_project/templates/nodepool/clouds.yaml.erb @@ -37,6 +37,7 @@ clouds: password: '<%= tripleo_password %>' project_name: '<%= tripleo_project %>' auth_url: 'https://ci-overcloud.rh1.tripleo.org:13000/v2.0' + has_network: False bluebox-sjc1: auth: username: '<%= bluebox_username %>'