Public bug reported:
Ignazio Cassano <ignaziocass...@gmail.com>
sab 15 mag, 19:41 (2 giorni fa)
a openstack-discuss
Hello Guys,
I've just upgraded from openstack queens to rocky and then to stein on centos 7.
In my configuration I have router high availability.
After the upgrade and rebooting each controller one by one I get the following
errors on all my 3 controllers under /var/log/neutron/l3-agent.log
http://paste.openstack.org/show/805407/
If I run openstack router show for for one of uuid in the log:
http://paste.openstack.org/show/805408/
Namespace for router in present on all 3 controllers.
After the controllers reboot,some routers lost their routing tables, but
restarting l3-agent they went ok.
The l3 agent respawning error, cause neutron to fill controller memory and the
controller stops to responding and it is fenced by the others.
So the router ha move some jobs to another controller and it fills its memory
and so on.
I stopped neutron services and I cleaned directory /var/lib/neutron/ha_confs
Restarting neutron services respawning errors disappeared but I had to create
again some router static routes (not all).
Probably it is a bug ?
Ignazio
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1928675
Title:
[stein][neutron] l3 agent error
Status in neutron:
New
Bug description:
Ignazio Cassano <ignaziocass...@gmail.com>
sab 15 mag, 19:41 (2 giorni fa)
a openstack-discuss
Hello Guys,
I've just upgraded from openstack queens to rocky and then to stein on centos
7.
In my configuration I have router high availability.
After the upgrade and rebooting each controller one by one I get the
following errors on all my 3 controllers under /var/log/neutron/l3-agent.log
http://paste.openstack.org/show/805407/
If I run openstack router show for for one of uuid in the log:
http://paste.openstack.org/show/805408/
Namespace for router in present on all 3 controllers.
After the controllers reboot,some routers lost their routing tables, but
restarting l3-agent they went ok.
The l3 agent respawning error, cause neutron to fill controller memory and
the controller stops to responding and it is fenced by the others.
So the router ha move some jobs to another controller and it fills its memory
and so on.
I stopped neutron services and I cleaned directory /var/lib/neutron/ha_confs
Restarting neutron services respawning errors disappeared but I had to create
again some router static routes (not all).
Probably it is a bug ?
Ignazio
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1928675/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
