This bug was fixed in the package keepalived - 1:1.2.2-3ubuntu2.12.10.1
---
keepalived (1:1.2.2-3ubuntu2.12.10.1) quantal-proposed; urgency=low
* debian/patches/05_fix_address_comparison.patch:
- Two different IPv4 addresses were returned to be
equal while this was not the
This bug was fixed in the package keepalived - 1:1.2.2-3ubuntu1.1
---
keepalived (1:1.2.2-3ubuntu1.1) precise-proposed; urgency=low
* debian/patches/05_fix_address_comparison.patch:
- Two different IPv4 addresses were returned to be
equal while this was not the case. (LP:
This bug was fixed in the package keepalived - 1:1.2.2-3ubuntu2.13.04.1
---
keepalived (1:1.2.2-3ubuntu2.13.04.1) raring-proposed; urgency=low
* debian/patches/05_fix_address_comparison.patch:
- Two different IPv4 addresses were returned to be
equal while this was not the
Let me clarify. Once the henrix kernel is installed, the normal and
proposed keepalived can be installed and tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload b
Confirmed. Once the henrix kernel [1] is installed the new keepalived
on Raring works.
$ apt-cache policy keepalived
keepalived:
Installed: 1:1.2.2-3ubuntu2.13.04.1
Candidate: 1:1.2.2-3ubuntu2.13.04.1
Version table:
*** 1:1.2.2-3ubuntu2.13.04.1 0
500 http://nova.clouds.archive.ubun
For Raring, the kernel panic is happening due to this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1238494
The patched kernel linked there fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
On a KVM guest the freeze happens upon starting the normal (non-
proposed) keepalived.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload buggy due to improper ipv4 addre
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ raring-proposed/main
amd64 -- maybe use the default archive to do your test instead of
nova.clouds?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12118
Hm, I tried again and it installed ok. I need more time to verify this.
Don't know what's going on.
$ apt-cache policy keepalived
keepalived:
Installed: 1:1.2.2-3u
There is something seriously wrong with the Raring package. Starting
keepalived caused my system to lock up. The same happened after trying
it on a few different platforms. My last attempt was with a traditional
KVM guest. After the freeze I reset the guest and I was able to capture
a screensho
** Tags added: verification-done-quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload buggy due to improper ipv4 address comparison
To manage notifications about t
Ditto for Quantal - all good.
$ sudo apt-cache policy keepalived
keepalived:
Installed: 1:1.2.2-3ubuntu2.12.10.1
Candidate: 1:1.2.2-3ubuntu2.12.10.1
Version table:
*** 1:1.2.2-3ubuntu2.12.10.1 0
500 http://nova.clouds.archive.ubuntu.com/ubuntu/ quantal-proposed/main
amd64 Packages
Obviously, the above verification was done for Precise. I will soon do
the same for Quantal and Raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload buggy due to i
I redid both tests (description) and re-confirmed both failures. I then
installed the -proposed version below and re-did the tests. They both
passed.
$ apt-cache policy keepalived
keepalived:
Installed: 1:1.2.2-3ubuntu1.1
Candidate: 1:1.2.2-3ubuntu1.1
Version table:
*** 1:1.2.2-3ubuntu1.1
** Branch linked: lp:ubuntu/precise-proposed/keepalived
** Branch linked: lp:~ubuntu-branches/ubuntu/quantal/keepalived/quantal-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
** Branch linked: lp:ubuntu/raring-proposed/keepalived
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload buggy due to improper ipv4 address comparison
To manage notific
Hello Peter, or anyone else affected,
Accepted keepalived into raring-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/keepalived/1:1.2.2-3ubuntu2.13.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Changed in: keepalived (Ubuntu Quantal)
Importance: Undecided => High
** Changed in: keepalived (Ubuntu Raring)
Importance: Undecided => High
** Changed in: keepalived (Ubuntu Precise)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ub
** Changed in: keepalived (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload buggy due to improper ipv4 address comparis
** Description changed:
[Impact]
There are at least 2 identified problems with keepalived on Precise when
trying to reload the configuration (/etc/keepalived/keepalived.conf):
(a) The removal of a server from the cluster does not work when the port
of that server is in use by another m
20 matches
Mail list logo
