After investigating further, I believe I am hitting the following issue:
https://bugs.launchpad.net/neutron/+bug/1995078
Essentially the external port and the LRP are being scheduled separately and
without coordination. Because of this, if these ports are scheduled on
different chassis the
On Wed, 31 Jan 2024 17:45:30 -0800
MIchael Miller via discuss wrote:
> Hi All,
>
> Not sure if this is the right forum for this question but figured I
> would start here.
>
> Have implemented several dedicated kvm based private virtualization
> server in several Outside Data Center (have
On 2/2/24 08:58, Lim, Derrick via discuss wrote:
> Hi Ilya Maximets,
>
>> The rules look mostly fine. I think the main problem you have is priority.
>> Default priority for OF rules (if not specified) is 32768, so your new rules
>> with priority 50 are too low in a priority list and not getting
On 2/1/24 04:42, Huangzhidong via discuss wrote:
> Hi
>
> When I use bond/show to get next balance time, it sometimes get a negative
> value.
>
> It can easily reproduce by run shell scripts:
>
> while true; do
> ovs-appctl bond/show | grep next
> done
>
> and it can be easily fixed by:
>
>
Hi
I configured static aggregation on the physical switch and also configured a
static aggregation bond port on the latest version of OVS. When I set the LACP
of the bond port to active, the port goes down, which is reasonable because the
protocols on both ends do not match. However, when I
Hi
When I use bond/show to get next balance time, it sometimes get a negative
value.
It can easily reproduce by run shell scripts:
while true; do
ovs-appctl bond/show | grep next
done
and it can be easily fixed by:
ofproto/bond.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Hi
I have two bridges, vds1-br and vds1-br-ex, connected by patch ports with OVS
3.2. When I configure RSTP on both bridges, it causes the OVS process to crash
and restart repeatedly.
[root@localhost ~]# ovs-vsctl set Bridge vds1-br-ex rstp_enable=true
[root@localhost ~]# ovs-vsctl set Bridge
