A fix will possibly be sent and packaged in 1.2.16. Maybe it will be backported to 1.2.14 and 1.2.15. We now have two choices:
1) Find a work around in Neutron. The only one I could find is to enable pre-emption, which has its set of pros and cons.
2) Wait until a fix lands, 1.2.16 is released and work with the distros to backport it to 1.2.14 and 1.2.15. Any deployments that are running the affected versions are screwed in the mean time.
keepalived 1.2.14 introduced a regression when running it in no-preempt mode. More details here in a thread I started on the keepalived-devel list: sourceforge. net/p/keepalive d/mailman/ message/ 33604497/
http://
A fix will possibly be sent and packaged in 1.2.16. Maybe it will be backported to 1.2.14 and 1.2.15. We now have two choices:
1) Find a work around in Neutron. The only one I could find is to enable pre-emption, which has its set of pros and cons.
2) Wait until a fix lands, 1.2.16 is released and work with the distros to backport it to 1.2.14 and 1.2.15. Any deployments that are running the affected versions are screwed in the mean time.