<div dir="ltr">Hi, <div><br></div><div>thank you for clarifying this to me and pointing to the bug report.</div><div><br></div><div>However, the issue I was getting at was that I can't reach the guests and get a "no route to host" error,</div>
<div>even though I can ping the gateway; I thought that adding the router to several l3-agents would solve this issue</div><div><br></div><div>(just like adding the dhcp agents from each compute hosts to each network has solved the issue that the guest VMs </div>
<div>were not getting their IP addresses)</div><div><br></div><div><br></div><div>Do you have any tips to troubleshoot the routing/connectivity to the guests?</div><div>As said, they do get their IP addresses (e.g. 10.0.101.3), I can ping the gateway (e.g. 10.0.101.1)</div>
<div>but when pinging the VM directly, I get a "no route to host" error.</div><div><br></div><div>cheers,</div><div>/Nicolae</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 6 September 2013 05:12, Jian Wen <span dir="ltr"><<a href="mailto:jian.wen@canonical.com" target="_blank">jian.wen@canonical.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">Hello,<div><br></div><div>In grizzly and havana, a router can only be hosted by a single l3 agent.</div>
<div><br></div><div>The related bug report is <a href="https://bugs.launchpad.net/neutron/+bug/1154622" target="_blank">https://bugs.launchpad.net/neutron/+bug/1154622</a></div>
<div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Fri, Sep 6, 2013 at 12:37 AM, BRINGARD, KEVIN <span dir="ltr"><<a href="mailto:kb718q@att.com" target="_blank">kb718q@att.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think Robert's comment is correct. The router is currently hosted on agent "789a77fd-52ff-44be-afea-27d26a8cd3d3". This was assigned at the router's creation by the router scheduler (currently only a chance scheduler exists, so it's random).<br>
<br>
You cannot host the same logical router on more than one l3-agent at once, which is likely why you're getting the error when you attempt to add the router to an L3-agent.<br>
<br>
If you want to specify which L3-agent is hosting a specific router, you would do something like the following:<br>
<br>
quantum l3-agent-list-hosting-router router01 <copy the agent ID, in this case: 789a77fd-52ff-44be-afea-27d26a8cd3d3><br>
quantum agent-list | grep L3<br>
<copy agent ID you want to move the router onto> quantum l3-agent-router-remove <agent ID the router is currently hosted on> <router-id> quantum l3-agent-list-hosting-router router01 <verify the router is no longer hosted on any L3-agent> quantum l3-agent-router-add <agent ID where you would like the router to be hosted> <router-id> quantum l3-agent-list-hosting-router router01 <verify the router is now hosted on the new l3-agent><br>
<br>
I personally would get router01's UUID and use that in place of the name router01, but it *should* work either way.<br>
<br>
But, to your original question, you shouldn't have to add the router to an agent as that should happen at router creation time by the scheduler (as Robert said).<br>
<span><font color="#888888"><br>
-- kevin<br>
</font></span><div><div><br>
<br>
-----Original Message-----<br>
From: Nicolae Paladi [mailto:<a href="mailto:n.paladi@gmail.com" target="_blank">n.paladi@gmail.com</a>]<br>
Sent: Thursday, September 05, 2013 3:19 AM<br>
To: Robert van Leeuwen<br>
Cc: <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Subject: Re: [Openstack] Error when calling l3-agent-router-add<br>
<br>
Hi,<br>
<br>
<br>
the output is:<br>
<br>
<br>
<br>
<br>
quantum l3-agent-list-hosting-router router01<br>
<br>
+--------------------------------------+---------------+----------------+-------+<br>
| id | host | admin_state_up | alive |<br>
+--------------------------------------+---------------+----------------+-------+<br>
| 789a77fd-52ff-44be-afea-27d26a8cd3d3 | seoul | True | :-) |<br>
+--------------------------------------+---------------+----------------+-------+<br>
<br>
<br>
However, shouldn't the l3-agent running on each compute host be attached to the router, or am I completely misunderstanding somethning?<br>
<br>
<br>
Thanks,<br>
/Nicolae.<br>
<br>
<br>
<br>
<br>
<br>
On 5 September 2013 11:14, Robert van Leeuwen <<a href="mailto:Robert.vanLeeuwen@spilgames.com" target="_blank">Robert.vanLeeuwen@spilgames.com</a>> wrote:<br>
<br>
<br>
> quantum l3-agent-router-add 789a77fd-52ff-44be-afea-27d26a8cd3d3 router01<br>
<br>
Not sure what you are trying to accomplish here.<br>
Scheduling, by default, happens automatically unless you have multiple routers and want to set it up to run a router on a specific l3-agent.<br>
<br>
Usually this should be enough:<br>
<br>
quantum router-create router1<br>
quantum router-interface-add router1 ${subnetname)<br>
<br>
What is the output of the following?:<br>
quantum l3-agent-list-hosting-router $(routername}<br>
<br>
Cheers,<br>
Robert van Leeuwen<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div></div><div><div>_______________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div dir="ltr">Cheers,<div>Jian</div></div>
</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">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>