Comment 22 for bug 1519641

I think I solved the problem here in my deployment.

Scenario: I'm following the Ubuntu Install Guide (http://docs.openstack.org/liberty/install-guide-ubuntu). But, I'm not using either option 1 or 2. I'm using the network scenario described in http://docs.openstack.org/liberty/networking-guide/scenario-dvr-ovs.html.

At controller, in /etc/nova/nova.conf, should exist a [neutron] section. In my case it was lacking the authentication parameters.

This section as below, without authentication parameters, was causing the problem:

[neutron]
service_metadata_proxy = True
metadata_proxy_shared_secret = password

With these authentication parameters, instances could be launched:

[neutron]
url = http://controller:9696
auth_strategy = keystone
admin_auth_url = http://controller:35357/v2.0
admin_tenant_name = service
admin_username = neutron
admin_password = NEUTRON_PASS

service_metadata_proxy = True
metadata_proxy_shared_secret = password

--

So, as the error message suggest, it was some problem with password sent to API. In my case was the lacking of some parameters in [neutron] section of nova.conf at controller. However, I think the code that raise the exception show a message like that, something about problems with password that API received. If no password is sent, the problem occurs.

I suggest who is facing this problem to check all configurations of components that use authentication parameters.

Thanks!