<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi All!<br>
<br>
I have a ambient with 3 hosts (Network, Controller and Node1
(Qemu)). I created an ambient based this tutorial
(<a class="moz-txt-link-freetext" href="http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html">http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html</a>).
My problem is when I create a instance. The instance Instance
doesn't get IP address.<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; white-space: pre-wrap;">checking <a class="moz-txt-link-freetext" href="http://169.254.169.254/20090404/instanceid">http://169.254.169.254/20090404/instanceid</a>
failed 1/20: up 187.68. request failed
failed 2/20: up 190.06. request failed
failed 3/20: up 192.24. request failed
failed 4/20: up 194.43. request failed
failed 5/20: up 196.61. request failed
failed 6/20: up 198.82. request failed
failed 7/20: up 201.03. request failed
failed 8/20: up 203.22. request failed
failed 9/20: up 205.42. request failed
failed 10/20: up 207.64. request failed
failed 11/20: up 209.87. request failed
failed 12/20: up 212.08. request failed
failed 13/20: up 214.29. request failed
failed 14/20: up 216.49. request failed
failed 15/20: up 218.70. request failed
failed 16/20: up 220.91. request failed
failed 17/20: up 223.13. request failed
failed 18/20: up 225.38. request failed
failed 19/20: up 227.62. request failed
failed 20/20: up 229.87. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 232.10. searched: nocloud configdrive ec2
failed to get instanceid of datasource
Starting dropbear sshd: generating rsa key... generating dsa key... OK
=== network info ===
ifinfo: lo,up,127.0.0.1,8,::1
ifinfo: eth0,up,,8,fe80::f816:3eff:fef3:2a6d
=== datasource: None None ===
</pre>
<br>
At the controller I received the warning:<br>
<br>
<br>
2013-09-04 00:40:44 WARNING
[quantum.scheduler.dhcp_agent_scheduler] No active DHCP agents<br>
2013-09-04 00:40:44 WARNING [quantum.db.agentschedulers_db] Fail
scheduling network {'status': u'ACTIVE', 'subnets':
[u'80b21701-4b05-4585-985a-60905ff42531'], 'name': u'public',
'provider:physical_network': None, 'admin_state_up': True,
'tenant_id': u'27d2b93f11ac4e91a3edb26edb28fb6b',
'provider:network_type': u'gre', 'router:external': True, 'shared':
False, 'id': u'b3e465b7-b5a2-45d5-8b24-aa8bea0ab0a0',
'provider:segmentation_id': 2L}<br>
<br>
And when I executed:<br>
<br>
<br>
root@cloud:~# quantum agent-list<br>
Unknown command ['agent-list']<br>
<br>
Other commands:<br>
<br>
root@cloud:~# nova-manage service list<br>
Binary Host
Zone Status State Updated_At<br>
nova-cert cloud
internal enabled :-) 2013-09-04 03:59:12<br>
nova-consoleauth cloud
internal enabled :-) 2013-09-04 03:59:12<br>
nova-scheduler cloud
internal enabled :-) 2013-09-04 03:59:12<br>
nova-conductor cloud
internal enabled :-) 2013-09-04 03:59:12<br>
nova-compute c01
nova enabled :-) 2013-09-04 03:59:04<br>
<br>
root@c01:~# nova list<br>
+--------------------------------------+---------+--------+------------------------+<br>
| ID | Name | Status |
Networks |<br>
+--------------------------------------+---------+--------+------------------------+<br>
| 2c704622-1b5f-4651-9553-51aabee9090c | test29 | ACTIVE |
public=xxx.xxx.xxx.xxx |<br>
<br>
I searched but I couldn't find any resolution. Anybody has this
problem?<br>
<br>
Cheers.<br>
<br>
Marcelo Dieder<br>
<br>
<br>
</body>
</html>