keepalived makes a floating IP available on more than one host after configuration reload

Status changed to 'Confirmed' because the bug affects multiple users.

Thank you for taking the time to report this bug and helping to make Ubuntu better.

In Ubuntu we do not update stable releases with new upstream versions in order to keep stable releases stable, and keepalived in Ubuntu does not currently have an exception on this. See https://wiki.ubuntu.com/StableReleaseUpdates for the policy and rationale.

We can still fix specific issues by backporting their fixes from newer upstream releases, so I'll turn this bug into one to track the specific issue you're facing.

We can have a separate bug to track the update of keepalived in the development release of Ubuntu (currently Wily) to a newer upstream release, but it doesn't sound like that'll help you since your focus is currently on 14.04.

Hi, based on your statement:
 This issue seems to be fixed in 1.2.17
Combined with the fact that current wily version of keepalived is 1.2.19-1 , I'm marking this 'fix released' in wily.

As Robie suggested above, I'll see if we can cherry pick a patch for 14.04 and possibly 15.04.

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)?

Hi,
  I've moved this to 'low' and un-assigned myself.
The easiest thing to do is probably to re-build your own newer version of keepalived if you're hitting this issue.

You can take the source version in wily and build it in a trusty ppa, or possibly even just install the wily deb in trusty.

Hi,

I came across this bug while doing a cleanup of old bugs (very old indeed). I took a look at what @smoser researched.

In the changelog of the requested version (1.2.17), there are 45 entries related to changes affecting VRRP: some are clearly not related to this bug, but some are not. Without steps to reproduce the issue is difficult to pick the correct fix (for me, in fact, I'll choose a different one than the one Scott chose -9fd19bf4e2cd271c2cebb546e9224f892cb88739-).

Please, provide all information you can give about this bug (steps to reproduce it, logs, errors/warning messages, configuration, ...). Until then, I'll mark this bug as "Incomplete" and you can change the bug status back to "New" when you provide that information.

Thanks in advance for taking the time on this.

Hi again,

by the way, Trusty reached EOSS (End of Standard Support) so I'm afraid it can't be fixed. It is unfortunate that we were unable to resolve this defect, however, there appears to be no further action possible at this time because it's not a security bug.

As the bug is solved in higher versions that are already incorporated to Ubuntu's newest series, I'll mark the bug as "Won't fix". Please, feel free to mark it as "New" if you consider the bug is affecting current versions.