Perhaps when the L3 agent starts up we can have it explicitly set the port status to DOWN for all of the HA ports on that node. Then we are guaranteed that when they go to ACTIVE it will be because the L2 agent has wired the ports.
On Fri, May 26, 2017 at 5:27 AM, Anil Venkata <anilvenk...@redhat.com> wrote: > This is regarding https://bugs.launchpad.net/neutron/+bug/1597461 > Earlier to fix this, we added code [1] to spawn keepalived only when HA > network port status is active. > > But, on reboot, node will get HA network port's status as ACTIVE from > server(please see comment [2]), > though l2 agent might not have wired[3] the port, resulting in spawning > keepalived. Any suggestions > how l3 agent can detect that l2 agent has not wired the port and > then avoid spawning keepalived? > > [1] https://review.openstack.org/#/c/357458/ > [2] https://bugs.launchpad.net/neutron/+bug/1597461/comments/26 > [3] l2 agent wiring means setting up ovs flows on br-tun to make port > usable > > Thanks > Anilvenkata > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
