I've tested the xenial-proposed package with Openstack Mitaka and confirm that it now behaves in the same way as 1.3.9 from Bionic i.e. if I kill the neutron state change agent then keepalived:
I see the same behavior in that when the l3agent respawns keepalived it does so prior to spawning the state change agent (a.k.a ip -o monitor) which results in (a) keepalived transitioning to backup (b) keepalived deconfiguring the vip, evip etc and (c) neutron never seeing the deconfigure since it happens prior to ip -o monitor being run (by neutron-keepalived-state-change). So (a) and (b) confirm this patch is good and (c) needs fixing in neutron.
I've tested the xenial-proposed package with Openstack Mitaka and confirm that it now behaves in the same way as 1.3.9 from Bionic i.e. if I kill the neutron state change agent then keepalived:
pkill -f "/usr/bin/ neutron- keepalived- state-change --router_ id=ROUTER_ UUID" neutron/ ha_confs/ ROUTER_ UUID/keepalived .conf"
pkill -f "/var/lib/
I see the same behavior in that when the l3agent respawns keepalived it does so prior to spawning the state change agent (a.k.a ip -o monitor) which results in (a) keepalived transitioning to backup (b) keepalived deconfiguring the vip, evip etc and (c) neutron never seeing the deconfigure since it happens prior to ip -o monitor being run (by neutron- keepalived- state-change) . So (a) and (b) confirm this patch is good and (c) needs fixing in neutron.