Yes, that's the bug that occurred to me too, for your symptom. I think that 
including that patch will solve the problem.

From: Miguel A Diaz Corchero
Sent: Friday, 9 October 2015 09:08
To: [email protected]; Kevin Benton
Subject: Re: [Openstack-operators] Inconsistent neutron namespaces after 
downtime


Kevin, now I see your patch of this bug

https://review.openstack.org/#/c/218852/

Miguel.




El 09/10/15 09:40, Miguel A Diaz Corchero escribió:
Thanks Kevin.

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:
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', 'brd', 'None', 'scope', 'global', 'dev', 
'qg-ee3cf43a-10']
Exit code: 1
Stdout: ''
Stderr: 'Error: an inet address is expected rather than "None".\n' execute 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:75

I see that a broadcast address is expected, for instance

ip netns exec qrouter-84a23b9d-cf74-435c-99a1-53b842209c73 ip -4 addr add 
192.168.7.204/32 brd 192.168.7.255 scope global dev qg-ee3cf43a-10

I continue searching for any solution.
Miguel.


El 08/10/15 19:23, Kevin Benton escribió:
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.

On Thu, Oct 8, 2015 at 7:45 AM, Miguel A Diaz Corchero 
<[email protected]<mailto:[email protected]>>
 wrote:
Hi all

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.

# ip netns exec qrouter-84a23b9d-cf74-435c-99a1-53b842209c73 iptables-save | 
grep 192.168.7.204
-A neutron-l3-agent-OUTPUT -d 192.168.7.204/32<http://192.168.7.204/32> -j DNAT 
--to-destination 10.100.1.14
-A neutron-l3-agent-PREROUTING -d 192.168.7.204/32<http://192.168.7.204/32> -j 
DNAT --to-destination 10.100.1.14
-A neutron-l3-agent-float-snat -s 10.100.1.14/32<http://10.100.1.14/32> -j SNAT 
--to-source 192.168.7.204
# ip netns exec qrouter-84a23b9d-cf74-435c-99a1-53b842209c73 ip addr | grep 
192.168.7.204
# (no ip)

Any idea to force the reload of these (floating-ips) interfaces in qrouters? 
(restarting the l3 agent doesn't solve the issue)

Miguel.

--
Miguel Angel Díaz Corchero
Systems Administrator / Researcher
c/ Sola nº 1; 10200 TRUJILLO, SPAIN
Tel: +34 927 65 93 17 Fax: +34 927 32 32 37<tel:%2B34%20927%2032%2032%2037>

[CETA-Ciemat logo]<http://www.ceta-ciemat.es/>


----------------------------
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.
----------------------------



_______________________________________________
OpenStack-operators mailing list
[email protected]<mailto:[email protected]>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




--
Kevin Benton




_______________________________________________
OpenStack-operators mailing list
[email protected]<mailto:[email protected]>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to