error when connecting to metadata service with neutron
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
Nachi Ueno |
Bug Description
When configured with neutron, I'm able to start a cirros instance and ssh to it, but it fails to connect to the metadata service. From the cirros console:
checking http://
failed 1/20: up 9.25. iid had '<html>
<head>
<title>500 Internal Server Error</title>
</head>
<body>
<h1>500 Internal Server Error</h1>
Remote metadata server experienced an internal server error.<br /><br />
From /opt/stack/
REQ: curl -i http://
http_log_req /opt/stack/
2013-08-13 13:03:45.559 10939 DEBUG neutronclient.
http_log_resp /opt/stack/
2013-08-13 13:03:45.560 10939 ERROR neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
2013-08-13 13:03:45.560 10939 TRACE neutron.
It looks like devstack is not setting the keystone authentication options in /etc/neutron/
# The Neutron user information for accessing the Neutron API.
auth_url = http://
auth_region = RegionOne
admin_tenant_name = %SERVICE_
admin_user = %SERVICE_USER%
admin_password = %SERVICE_PASSWORD%
Here's what my localrc looks like:
# Default passwords
ADMIN_PASSWORD=
MYSQL_PASSWORD=
RABBIT_
SERVICE_
SERVICE_
SCREEN_
HOST_IP=
#
# Quantum
#
# https:/
disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service neutron
PUBLIC_
Q_FLOATING_
FLOATING_
Q_USE_SECGROUP=
I'm running ubuntu 12.04 inside of VirtualBox.
Changed in devstack: | |
status: | New → In Progress |
Changed in neutron: | |
milestone: | none → havana-3 |
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | havana-3 → 2013.2 |
I think this is a duplicate of https:/ /bugs.launchpad .net/neutron/ +bug/1210664
Supposedly, this was fixed in bf10ac55a99d226 a81bdbc7e6bd1e8 5b4f48652d
However, my cirros instance still can't retrieve metadata. Now the console says "request failed" rather than seeing a 500 error:
checking http:// 169.254. 169.254/ 2009-04- 04/instance- id
failed 1/20: up 9.58. request failed
failed 2/20: up 21.93. request failed
failed 3/20: up 34.05. request failed
failed 4/20: up 46.17. request failed
failed 5/20: up 58.28. request failed
failed 6/20: up 70.48. request failed
failed 7/20: up 82.64. request failed
failed 8/20: up 94.84. request failed
failed 9/20: up 107.07. request failed
failed 10/20: up 119.18. request failed
failed 11/20: up 131.38. request failed
failed 12/20: up 143.51. request failed
failed 13/20: up 155.68. request failed
failed 14/20: up 167.88. request failed
failed 15/20: up 179.99. request failed
failed 16/20: up 192.22. request failed
failed 17/20: up 204.33. request failed
failed 18/20: up 216.45. request failed
failed 19/20: up 228.57. request failed
failed 20/20: up 240.76. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 253.15. searched: nocloud configdrive ec2