thanks for the info!
** Changed in: quantum
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1186753
Title:
Floodlight-grizzly-2013-1-1-host routes not getting into VM instance
Status in OpenStack Quantum (virtual network service):
Invalid
Bug description:
Using Grizzly 2013-1-1 release
Configuration: 1-Controller/1-Network/1-Compute nodes
Floodlight controller and OpenVSwitch
NO quantum-l3 service
In dhcp_agent.ini, the following are set:
enable_isolated_metadata =True
enable_metadata_network =False
Created a quantum network and subnet with host routes, 169.254.169.254/32 and
next hop dhcp-agent-ip-address.
This added host routes to quantum dhcp instance opts file.
However, when VM is launched, it does not reach this route. This does not
seem to get injected into VM. When accessing metadata service, VM shows "No
route to host" for wget http://169.254.169.254/20090404/metadata/instanceid
So, manually added the route info in the VM instance,
After adding, it is able to reach nova-metadata service running in the
controller. But, says, 400 BAD request. InstanceId is missing
<html>
<head>
<title>400 Bad Request</title>
</head>
<body>
<h1>400 Bad Request</h1>
X-Instance-ID header is missing from request.<br /><br />
</body>
To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1186753/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
