"500 error" failed to get instance-id of datasource
We are unable to access the instance with key pair. On checking the logs we found that meta data is not working properly. We are getting 500 internal error while running the curl command from inside the instance. We are running neutron-metadata-agent on neutron server. I have configured the meta data as per suggestions still no success. We have "service" tenant in openstack , there is no tenant with "services" . We follow the openstack guide for installing Icehouse on ubuntu 12.04. We are running ML2+GRE+OVS
There is no /etc/neutron/metadata_agent.ini on controller node. Should it be present on controller ?
Please find the logs below and /etc/neutron/metadata_agent.ini file content from neutron server.
Neutron /etc/neutron/metadata_agent.ini
verbose = True
auth_url = http://192.168.10.2:5000/v2.0
auth_region = RegionOne
admin_tenant_name = service
admin_user = neutron
admin_password = de65e97a4e135
nova_metadata_ip = 192.168.10.2
metadata_proxy_shared_secret = 63797d4fereh48f7c8
nova_metadata_port = 8775
metadata_workers = 0
Nova.conf output from controller
# cat /etc/nova/nova.conf | grep metadata | grep -v ^#
enabled_apis=ec2,osapi_compute,metadata
service_neutron_metadata_proxy = true
neutron_metadata_proxy_shared_secret = 63797d4fereh48f7c8
metadata_host = 192.168.10.2
metadata_listen = 0.0.0.0
metadata_workers=2
metadata_listen_port=8775
curl http://169.254.169.254/2009-04-04/instance-id
<head>
<title>500 Internal Server Error</title>
</head>
<body>
500 Internal Server Error
Remote metadata server experienced an internal server error.
On controller
$ netstat -lntp | grep 8775
tcp 0 0 0.0.0.0:8775 0.0.0.0:* LISTEN 28072/python
$ netstat -lntp | grep 9697
$ ps -ef | grep 28072
nova 28072 1 1 11:23 ? 00:00:14 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28157 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28158 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28159 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28160 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28161 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28162 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28163 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28164 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28180 28072 0 11:23 ? 00:00:01 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28181 28072 0 11:23 ? 00:00:02 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28182 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr/bin/nova-api --config-file=/etc/nova/nova.conf
nova 28183 28072 0 11:23 ? 00:00:00 /usr/bin/python /usr ...
If neutron-metadata-agent runs on Controller. Answer is yes
Port 5000 is incorrect, not space. Focus your attention.
Hi,
Will Iptables cause any issue on compute controller or neutron ?
What reports /var/log/nova/nova-compute.log on Compute Node during VM booting UP ? Please,post.
guys: thank you both for the time you're taking to fix this issue. Please try to keep this site usable: update questions and answers while you go, use comments only for short comments (should be limited to 200 chars)