So, just taking a look here, it seems not terribly trivial to cherry pick a fix back to trusty's 1.2.7, especially without a recreate description.
Looking at git changelogs, I suspect that your issue was intended to be fixed by: https://github.com/acassen/keepalived/commit/7bf6fc But then that was referenced as a buggy commit in https://github.com/acassen/keepalived/commit/97eb4e The code in ipwrapper.c seems to have been fairly volatile Digging a bit, I put together a patch of the 2 commits above, but those are dependent on other patches. 90d4eee1 for realserver_t->reloaded and virtual_server_t->reloaded 09de4419 for virtual_server_t->vsg its probably possible to do this cherry pick, but at very least its non-trivial. Do you have a feeling or knowledge as to if I've identified the upstream fix correctly (7bf6fc)? -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/1481337 Title: keepalived makes a floating IP available on more than one host after configuration reload Status in keepalived package in Ubuntu: Fix Released Status in keepalived source package in Trusty: Confirmed Status in keepalived source package in Vivid: Confirmed Status in keepalived source package in Wily: Fix Released Bug description: The version in 14.04 is 1:1.2.7-1ubuntu1 There's an issue with reloading the configuration file, where the state of VRRP gets 'confused' (in lack of a better description), resulting in a floating IP being available on more than one host. This issue seems to be fixed in 1.2.17. Since the package hasn't had an update in over 2 years, I kindly request it to be updated to at least 1.2.17 For more information, see http://www.keepalived.org/changelog.html Extra info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 1:1.2.7-1ubuntu1 3) What you expected to happen Keepalived config reloaded without interruption of services. VRRP should notice VIP being present on one host and do nothing. 4) What happened instead Keepalived config was reloaded but VRRP decided to activate the VIP on the host that didn't have it previously. Resulting in routing errors etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1481337/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
