[Expired for keepalived (Ubuntu) because there has been no activity for
60 days.]
** Changed in: keepalived (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Looks like this is the real cause of these problems -
https://bugs.launchpad.net/neutron/+bug/1793102
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789045
Title:
keepalived 1:1.2.24-1ubuntu0.16.04.
Hi team,
ı also have this problem. I explained with details in
https://bugs.launchpad.net/neutron/+bug/1793118.
I think keepalived 1:1.2.24-1ubuntu0.16.04.1 is broken. When I look at
keepalived logs, it says "Unable to load ipset library". May be error is about
that. Logs are in http://paste.ope
We have potentially hit similar behaviour to the mentioned issue and it
seems to occur when we enable the ha_vrrp_health_check_interval. I see
that this is enabled by default in the upstream tests [1] so I wonder if
this is somehow related.
[1]
https://github.com/openstack/neutron/blob/stable/quee
** Changed in: keepalived (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789045
Title:
keepalived 1:1.2.24-1ubuntu0.16.04.1 breaks Neutron stable bran
Added some further notes in
https://bugs.launchpad.net/neutron/+bug/1788185, hopefully someone can
continue from there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789045
Title:
keepalived 1:1.2.
The stable/queens tests in OpenStack run with pike UCA. Since there
seems to be no updated keepalived version in that repo, it means that
they are using 1:1.2.24-1ubuntu0.16.04.1.
I tested things manually a bit and it seems like the neutron test might
be trying to verify the broken behaviour of 1.
Hi again Slawek,
Just for some further details, the new versions of keepalived came about due
to:
https://bugs.launchpad.net/cloud-archive/+bug/1744062. In particular, see
https://bugs.launchpad.net/cloud-archive/+bug/1744062/comments/14 for the
descriptions of the commits that are included to
Hi Slawek, could you please provide a bit more detail about what you
expect to see vs. what you see with the new version of keepalived?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789045
Title:
k
Slawek, for stable/queens, can you confirm the version of keepalived
that your tests are running with? The queens cloud archive has
keepalived 1:1.3.9-1ubuntu0.18.04.1~cloud0, however I'm wondering if
you're running with the base xenial version of
1:1.2.24-1ubuntu0.16.04.1.
--
You received this b
Slawek, Thank you for reporting this issue. The new keepalived versions
include a cherry-pick of
https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c.
I'm currently building a new xenial version of keepalived in a PPA for
testing purposes with this patch removed. Wo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: keepalived (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789045
Title:
12 matches
Mail list logo
