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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481337 Title: keepalived makes a floating IP available on more than one host after configuration reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1481337/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
