<div dir="ltr">Hi Marcelo,<div><br>I might have a solution to the "not getting an IP address" problem, at least it works for me; </div><div>so, briefly, I use network type VLAN (should not make a difference, not sure) on 3 nodes atm<br>
(one controller/network (A), + two compute hosts (B, C));</div><div><br></div><div>I went the "diagnostic" way, with trial and error and came to the conclusion that my guests DO get an IP adress<br>when the dhcp-agent running on the respective compute host appears when in the list for that net:<br>
<br></div><div>how to reproduce:</div><div><b>quantum agent-list | grep DHCP</b></div><div>(you get a table with DHCP agents on different hosts)</div><div><br></div><div><b>quantum dhcp-agent-list-hosting-net <net1></b> -- you see which<br>
</div><div>dhcp agents are "attached" (don't know how to express it otherwise) to network</div><div><net1>.</div><div><br></div><div>So, when a guest is scheduled on <net1> and on host B and the dhcp-agent running on host B appears in</div>
<div>the list when calling, quantum dhcp-agent-list-hosting-net <net1>, then the instance gets the IP address.</div><div><br></div><div>If if it's not listed, the instance will not get an Ip address. </div><div>
calling </div><div><br></div><div><b>quantum dhcp-agent-network-add <dhcp-agent-on-host-B> <net1> </b></div><div><br></div><div>fixes the problem for me.</div><div><br></div><div>These are just observations, I don't know how the causes and what is the "normal" behavior.</div>
<div>Also, even though they do get the IP, I can't reach these instances from the outside (I suspect</div><div>this has to do with the l3-agent).</div><div><br></div><div>/Nicolae.</div><div><br></div><div><br></div><div>
<br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 6 September 2013 16:29, Marcelo Dieder <span dir="ltr"><<a href="mailto:marcelodieder@gmail.com" target="_blank">marcelodieder@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000099">
The python-quantumclient also has different versions at the two
guides.<span class="HOEnZb"><font color="#888888"><br>
<br>
Marcelo Dieder</font></span><div><div class="h5"><br>
<br>
<div>On 09/06/2013 11:26 AM, Marcelo Dieder
wrote:<br>
</div>
<blockquote type="cite">
Hi Nicolae,<br>
<br>
Apparently I have not located the problem, but I followed the
tutorial and now the quantum agent-list command worked.<br>
<br>
I made a comparison with the packages and guide <a href="http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html" target="_blank">http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html</a>
The difference between the two seems to be in openvswitch packages
and kernel version. Guide in DOCS OpenStack seems the packages are
incompatible and commands such as quantum-agent that doesn't
exist.<br>
<br>
Guide:
<a href="https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst" target="_blank">https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst</a><br>
<br>
Packages: <br>
<br>
quantum-plugin-openvswitch:amd64 (2013.1.2-0ubuntu1~cloud0,
automatic)<br>
quantum-l3-agent:amd64 (2013.1.2-0ubuntu1~cloud0)<br>
quantum-dhcp-agent:amd64 (2013.1.2-0ubuntu1~cloud0)<br>
quantum-plugin-openvswitch-agent:amd64 (2013.1.2-0ubuntu1~cloud0)<br>
python-quantumclient:amd64 (2.2.0-0ubuntu1~cloud0, automatic)<br>
python-quantum:amd64 (2013.1.2-0ubuntu1~cloud0, automatic)<br>
quantum-metadata-agent:amd64 (2013.1.2-0ubuntu1~cloud0)<br>
quantum-common:amd64 (2013.1.2-0ubuntu1~cloud0, automatic)<br>
openvswitch-switch:amd64 (1.4.0-1ubuntu1.5)<br>
openvswitch-common:amd64 (1.4.0-1ubuntu1.5, automatic)<br>
openvswitch-datapath-dkms:amd64 (1.4.0-1ubuntu1.5)<br>
<br>
root@network:~# lsb_release -a<br>
No LSB modules are available.<br>
Distributor ID: Ubuntu<br>
Description: Ubuntu 12.04.3 LTS<br>
Release: 12.04<br>
Codename: precise<br>
root@network:~# uname -r<br>
3.5.0-39-generic<br>
<br>
APT Sources<br>
<br>
deb <a href="http://ubuntu-cloud.archive.canonical.com/ubuntu" target="_blank">http://ubuntu-cloud.archive.canonical.com/ubuntu</a>
precise-updates/grizzly main<br>
<br>
<br>
Guide:
<a href="http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html" target="_blank">http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html</a><br>
<br>
quantum-plugin-openvswitch:amd64 (2013.1.2-0ubuntu1~cloud0,
automatic)<br>
quantum-l3-agent:amd64 (2013.1.2-0ubuntu1~cloud0)<br>
quantum-dhcp-agent:amd64 (2013.1.2-0ubuntu1~cloud0)<br>
quantum-plugin-openvswitch-agent:amd64 (2013.1.2-0ubuntu1~cloud0)<br>
python-quantumclient:amd64 (3.0.a1-1, automatic)<br>
python-quantum:amd64 (2013.1.2-0ubuntu1~cloud0, automatic)<br>
quantum-metadata-agent:amd64 (2013.1.2-0ubuntu1~cloud0, automatic)<br>
quantum-common:amd64 (2013.1.2-0ubuntu1~cloud0, automatic)<br>
openvswitch-switch:amd64 (1.4.2+git20120612-9.1~deb7u1)<br>
openvswitch-common:amd64 (1.4.2+git20120612-9.1~deb7u1, automatic)<br>
openvswitch-datapath-dkms:amd64 (1.4.2+git20120612-9.1~deb7u1)<br>
<br>
root@network:~# lsb_release -a<br>
No LSB modules are available.<br>
Distributor ID: Ubuntu<br>
Description: Ubuntu 12.04.3 LTS<br>
Release: 12.04<br>
Codename: precise<br>
root@network:~# uname -r<br>
3.2.0-52-generic<br>
<br>
APT Sources<br>
<br>
deb <a href="http://ubuntu-cloud.archive.canonical.com/ubuntu" target="_blank">http://ubuntu-cloud.archive.canonical.com/ubuntu</a>
precise-updates/grizzly main<br>
deb <a href="http://archive.gplhost.com/debian" target="_blank">http://archive.gplhost.com/debian</a>
grizzly main<br>
deb <a href="http://archive.gplhost.com/debian" target="_blank">http://archive.gplhost.com/debian</a>
grizzly-backports main<br>
<br>
After I set everything up again with guide mseknibilel, the
quantum agent-list works, and the instance can finally get the IP.
An important issue to be checked is whether the network interfaces
of the bridges are in promiscuous mode on the hypervisor. In my
case I use XenServer 6.2, I had to enable promisc mode interfaces
VIF and PIF. <br>
<br>
Do you have any logs with errors?<br>
<br>
Thanks for all.<br>
<br>
Marcelo Dieder<br>
<br>
<div>On 09/06/2013 07:20 AM, Nicolae
Paladi wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Marcelo,
<div><br>
</div>
<div>I have the same issue (I'm on CentOS 6.4 though); have
you found a solution?</div>
<div> </div>
<div>There was a similar thread earler: <a href="http://openstack.redhat.com/forum/discussion/230/warning-quantum-db-agentschedulers_db-fail-scheduling-network/p1" target="_blank">http://openstack.redhat.com/forum/discussion/230/warning-quantum-db-agentschedulers_db-fail-scheduling-network/p1</a></div>
<div>Make sure that all agents are up in 'quantum agent-list'<br>
</div>
<div><br>
</div>
<div>Also, in your quantum/server.log, do you get something
like:</div>
<div>WARNING [quantum.api.extensions] Extension
routed-service-insertion not supported by any of loaded
plugins<br>
</div>
<div><br>
</div>
<div>I am trying to understand if this is a related problem or
something that can be ignored atm;</div>
<div><br>
</div>
<div>I can say that after some fiddling with the quantum dhcp
agents my instances were getting an IP address and I could
reach them yesterday, but</div>
<div>apparently that wasn't very stable and today I'm back
with the same issue. </div>
<div><br>
</div>
<div>cheers,</div>
<div>/Nicolae</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 5 September 2013 03:42, happy idea
<span dir="ltr"><<a href="mailto:guolongcang.work@gmail.com" target="_blank">guolongcang.work@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Are you sure you had follow this page'guide
? <a href="http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_network.html" target="_blank">http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_network.html</a></div>
<div>
<div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2013/9/5 Marcelo Dieder <span dir="ltr"><<a href="mailto:marcelodieder@gmail.com" target="_blank">marcelodieder@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000099"> Hi, yes,
I have dnsmasq installed on Network Node.<br>
<br>
root@network:~# apt-get install dnsmasq<br>
Reading package lists... Done<br>
Building dependency tree <br>
Reading state information... Done<br>
dnsmasq is already the newest version.<br>
0 upgraded, 0 newly installed, 0 to remove and
0 not upgraded.<br>
<br>
<br>
root@network:~# ps aux | grep -i dnsmasq<br>
<br>
dnsmasq 3807 0.0 0.1 28820 980 ?
S 15:29 0:00 /usr/sbin/dnsmasq -x
/var/run/dnsmasq/dnsmasq.pid -u dnsmasq -r
/var/run/dnsmasq/resolv.conf -7
/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new<br>
<br>
nobody 26040 0.0 0.2 28820 1004 ?
S 15:45 0:00 dnsmasq --no-hosts
--no-resolv --strict-order --bind-interfaces
--interface=tap91e05e25-7f
--except-interface=lo
--pid-file=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/pid
--dhcp-hostsfile=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/host
--dhcp-optsfile=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/opts
--dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update
--leasefile-ro
--dhcp-range=set:tag0,10.5.5.0,static,120s
--conf-file= --domain=openstacklocal<br>
<br>
root 26041 0.0 0.0 28792 244 ?
S 15:45 0:00 dnsmasq --no-hosts
--no-resolv --strict-order --bind-interfaces
--interface=tap91e05e25-7f
--except-interface=lo
--pid-file=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/pid
--dhcp-hostsfile=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/host
--dhcp-optsfile=/var/lib/quantum/dhcp/a8f7c937-e8d0-4952-bff6-7d364335df22/opts
--dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update
--leasefile-ro
--dhcp-range=set:tag0,10.5.5.0,static,120s
--conf-file= --domain=openstacklocal<br>
<br>
I restarted the service dnsmasq, but occured
the same problem when I started a new
instance.<br>
<br>
2013-09-04 15:39: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>
2013-09-04 15:47:00 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>
Thanks.<span><font color="#888888"><br>
Marcelo Dieder</font></span>
<div>
<div><br>
<br>
<div>On 09/04/2013 11:15 AM, Hathaway.Jon
wrote:<br>
</div>
<blockquote type="cite">
<div>Do you have dnsmasq installed? I
found that it isnt installed as a
dependency. Without it i never
received dhcp either.<br>
<br>
Sent from my iPhone</div>
<div><br>
On Sep 3, 2013, at 10:31 PM, "happy
idea" <<a href="mailto:guolongcang.work@gmail.com" target="_blank">guolongcang.work@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">you didn't install
the dhcp agent, please refer to
this guide <a href="https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst" target="_blank">https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst</a></div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2013/9/4
Marcelo Dieder <span dir="ltr"><<a href="mailto:marcelodieder@gmail.com" target="_blank">marcelodieder@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div 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 href="http://docs.openstack.org/grizzly/basic-install/apt/content/basic-install_controller.html" target="_blank">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>
<pre style="line-height:normal;text-indent:0px;letter-spacing:normal;text-align:start;font-variant:normal;text-transform:none;font-style:normal;white-space:pre-wrap;word-wrap:break-word;font-weight:normal;word-spacing:0px">
checking <a href="http://169.254.169.254/20090404/instanceid" target="_blank">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.<span><font color="#888888"><br>
<br>
Marcelo Dieder<br>
<br>
<br>
</font></span></div>
<br>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></span><br>
<span>Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a></span><br>
<span>Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></span><br>
</div>
</blockquote>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>