<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Thanks Kevin. <br>
<br>
The router seems correctly schedule to the agent. After doing more
tests, I realised the issue also happens when I try to link a new
floating-ip. This is the log:<br>
<small>Command: ['sudo', 'neutron-rootwrap',
'/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec',
'qrouter-84a23b9d-cf74-435c-99a1-53b842209c73', 'ip', '-4',
'addr', 'add', '192.168.7.204/32', <b>'brd', 'None'</b>,
'scope', 'global', 'dev', 'qg-ee3cf43a-10']<br>
Exit code: 1<br>
Stdout: ''<br>
Stderr: 'Error: an inet address is expected rather than
"None".\n' execute
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:75</small><br>
<br>
I see that a broadcast address is expected, for instance <br>
<br>
<small>ip netns exec qrouter-84a23b9d-cf74-435c-99a1-53b842209c73
ip -4 addr add 192.168.7.204/32 <b>brd 192.168.7.255</b> scope
global dev qg-ee3cf43a-10</small><br>
<br>
I continue searching for any solution.<br>
Miguel.<br>
<br>
<br>
El 08/10/15 19:23, Kevin Benton escribió:<br>
</div>
<blockquote
cite="mid:CAO_F6JNpc6kADRnc1z8eT=UvjyJjpWKfHp0UPUe65P1bAs9RbQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">Is the router still scheduled to that l3 agent? The
issue could be that the router was rescheduled do to the
downtime and those are just leftover iptables rules.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 8, 2015 at 7:45 AM, Miguel
A Diaz Corchero <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:miguelangel.diaz@externos.ciemat.es"
target="_blank">miguelangel.diaz@externos.ciemat.es</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="#000000"> Hi all<br>
<br>
After a downtime of neutron I noticed that the
floating-ips (already created) are not included as
interfaces in qrouter. The iptables in qrouter were
perfectly set. <br>
<br>
<small># ip netns exec
qrouter-84a23b9d-cf74-435c-99a1-53b842209c73
iptables-save | grep 192.168.7.204<br>
-A neutron-l3-agent-OUTPUT -d <a moz-do-not-send="true"
href="http://192.168.7.204/32" target="_blank">192.168.7.204/32</a>
-j DNAT --to-destination 10.100.1.14<br>
-A neutron-l3-agent-PREROUTING -d <a
moz-do-not-send="true" href="http://192.168.7.204/32"
target="_blank">192.168.7.204/32</a> -j DNAT
--to-destination 10.100.1.14<br>
-A neutron-l3-agent-float-snat -s <a
moz-do-not-send="true" href="http://10.100.1.14/32"
target="_blank">10.100.1.14/32</a> -j SNAT --to-source
<b>192.168.7.204</b><br>
# ip netns exec
qrouter-84a23b9d-cf74-435c-99a1-53b842209c73 ip addr |
grep 192.168.7.204<br>
#<small> </small><b>(no ip)</b></small><br>
<br>
Any idea to force the reload of these (floating-ips)
interfaces in qrouters? (restarting the l3 agent doesn't
solve the issue)<br>
<br>
Miguel.<br>
<br>
<div>-- <br>
<i><font size="2"><span style="color:#000000"><span
style="font-family:Century Gothic,sans-serif,10">Miguel
Angel Díaz Corchero</span></span></font></i><font
size="2"><br>
<i><b><span style="font-family:Century
Gothic,sans-serif">Systems Administrator /
Researcher</span></b></i><br>
<i><span style="font-family:Century Gothic,sans-serif">c/
Sola nº 1; 10200 TRUJILLO, SPAIN</span></i><br>
<i><span style="font-family:Century Gothic,sans-serif">Tel:
+34 927 65 93 17 Fax: <a moz-do-not-send="true"
href="tel:%2B34%20927%2032%2032%2037"
value="+34927323237" target="_blank">+34 927 32
32 37</a></span></i>
<p><span><a moz-do-not-send="true"
href="http://www.ceta-ciemat.es/"
target="_blank"><img
src="cid:part6.08020705.00070401@externos.ciemat.es"
alt="CETA-Ciemat logo" height="76" border="0"
width="383"></a></span></p>
</font></div>
<pre><i><font color="black" face="Times New Roman, Times, serif" size="-1">
----------------------------
Confidencialidad:
Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener información privilegiada o
confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está
prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique
inmediatamente respondiendo al mensaje y proceda a su destrucción.
Disclaimer:
This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received
this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and
may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately.
----------------------------
</font></i>
</pre>
</div>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div>Kevin Benton</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>