Ask Your Question

Metadata Proxy server() got an unexpected keyword argument 'socket_timeout'

asked 2015-05-04 01:56:10 -0500

humankind135 gravatar image

Hi All,

Thanks for any help in advance, I have been banging my head against this for a few days and I'm no closer to sorting it than I was before. The metadata service is not accessible to instances and I cannot find anything listening on 80.

Every time I restart the l3 Agent I get the log at in /var/log/neutron/neutron-ns-metadata-proxy-

Configs at

Can anyone help, is there anything I am doing wrong?

Thanks James

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2015-05-05 08:40:52 -0500

dbaxps gravatar image

I believe metadata-agent.ini is incorrect sample bellow (Kilo on Ubuntu 14.04 via devstack)

root@ubuntu-System:/etc/neutron# cat metadata_agent.ini | grep -v ^$ | grep -v ^#
signing_dir = /var/cache/neutron
cafile = /opt/stack/data/ca-bundle.pem
auth_uri =
project_domain_id = default
project_name = service
user_domain_id = default
password = secret
username = neutron
auth_plugin = password
root_helper = sudo /usr/local/bin/neutron-rootwrap /etc/neutron/rootwrap.conf
nova_metadata_ip =
debug = True
verbose = True
auth_url =
auth_region = RegionOne
admin_tenant_name = %SERVICE_TENANT_NAME%
admin_user = %SERVICE_USER%
admin_password = %SERVICE_PASSWORD%
root_helper_daemon = sudo /usr/local/bin/neutron-rootwrap-daemon /etc/neutron/rootwrap.conf
edit flag offensive delete link more

answered 2015-05-09 04:24:10 -0500

humankind135 gravatar image

Just to Document this, I ended up editing /usr/lib/python2.7/dist-packages/neutron/ and removing the parameter from the class. Not the best solution but its woking now.

I was trying to use the juno and jessie-juno-backports repos from on debian jessie.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2015-05-04 01:56:10 -0500

Seen: 217 times

Last updated: May 09 '15