It appears the following commits are required to fix this for
keepalived:
commit e90a633c34fbe6ebbb891aa98bf29ce579b8b45c
Author: Quentin Armitage
Date: Fri Dec 15 21:14:24 2017 +
Fix removing left-over addresses if keepalived aborts
Issue #718 reported that if keepalived
It appears the following commits are required to fix this for
keepalived:
commit e90a633c34fbe6ebbb891aa98bf29ce579b8b45c
Author: Quentin Armitage
Date: Fri Dec 15 21:14:24 2017 +
Fix removing left-over addresses if keepalived aborts
Issue #718 reported that if keepalived
As reported by Xav in https://bugs.launchpad.net/ubuntu/+bug/1731595:
"Comment for the folks that are noticing this as 'fix released' but
still affected - see
https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c
for the rest of this fix, we need keepalived to be
As reported by Xav in https://bugs.launchpad.net/ubuntu/+bug/1731595:
"Comment for the folks that are noticing this as 'fix released' but
still affected - see
https://github.com/acassen/keepalived/commit/e90a633c34fbe6ebbb891aa98bf29ce579b8b45c
for the rest of this fix, we need keepalived to be
VRRP heart beat lose may cause the multiple active router behavior. The
underlying connectivity is key point for this. A monitoring for such
behavior is also necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Our environment is experiencing the same behavior.
Ocata on 16.04 - around 320 routers, some have 2 agents per router,
others have 3 agents per router.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We experience the same issue although we have a smaller environment with
only around 40 Neutron router running HA (two agents per router) over
three physical controllers running Ocata on Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@cgregan I think this is really a situation where the desired
scale/density is at odds with the fundamental design of neutron HA
routers. It's not something to address in the charms or in the
packaging. As such, I'd consider this a feature request, against
upstream Neutron, and I don't have an
We need an assigned engineer to meet the requirements of Field High SLA.
Please assign
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
L3 HA: multiple agents are active at the same
Just as another thing to consider - the deployment where this is
happening also experienced bug 1749425 which resulted in packet loss;
the networks between network/gateway units is also made via OVS, so if
OVS was dropping packets due to the large number of missing tap devices,
its possible this
Downgrading to Field High - I think the Critical part is tracked in LP
#1749425
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
L3 HA: multiple agents are active at the same time
To
FYI: Resubscribing field SLA. It was not raised as critical by Kiko R.;
I raised it and it's still an active ongoing problem on a customer site.
Please do not unsubscribe again without discussion with the correct
people.
--
You received this bug notification because you are a member of Ubuntu
I do think this issue is still of high importance to OpenStack's overall
scale and resilience story.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
L3 HA: multiple agents are active
FYI: Unsubscribing field SLA based on re-triage with Kiko R.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
L3 HA: multiple agents are active at the same time
To manage
I have some thoughts in my mind for this problem as below:
1, First of all, we need to figure out why it will appear multiple
ACTIVE master HA nodes in theory ?
Assume the master is dead (at this time, it's status in DB is still
ACTIVE), then slave will be selected to new master. After the old
This bug falls under the Canonical Cloud Engineering service-level
agreement (SLA) process, as a field critical bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
L3 HA: multiple
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744062
Title:
L3 HA: multiple agents are active at the same time
To manage notifications about this bug go to:
17 matches
Mail list logo
