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: *openstack-operators@lists.openstack.org; Kevin Benton
*Subject: *Re: [Openstack-operators] Inconsistent neutron namespaces
after downtime
Kevin,
stent 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
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
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-435
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 <
miguelangel.d...@externos.ciemat.es> wrote:
> Hi all
>
> After a downtime of n
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-OUTP
