yahoo-eng-team team mailing list archive

[李亚冲 <2058433@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

a public network with multi subnets , but based on ovn, They can't
communicate with each other

Hi, I think it's not a bug, or it's a logical bug, when I change my
mechanism_driver from openvswitch to ovn, I've been troubled by this
matter for a long time.

ok, my scenario: I applied a subnets from ISP provider, let's call it
subnet1 of public_network , After a period of time, the subnet IP is not
enough, So I applied for another subnets, let's call it subnet2 of
public_network. until now, the public_network will have two subnet.

But FIPs based on two subnets cannot communicate with each other, The
FIP of the subnet2 cannot communicate with itself either.

I found some bug reports :
<https://bugzilla.redhat.com/show_bug.cgi?id=1920025><https://access.redhat.com/errata/RHBA-2022:9044>
<https://bugzilla.redhat.com/show_bug.cgi?id=1929901> , but those think
it's a ovn bug.

And in my test, I' found it's a neutron logical bug, yes or no, it's a
bug, ha

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2058433

Title:
  a public network with multi subnets , but based on ovn, They can't
  communicate with each other

Status in neutron:
  New

Bug description:
  a public network with multi subnets , but based on ovn, They can't
  communicate with each other

  Hi, I think it's not a bug, or it's a logical bug, when I change my
  mechanism_driver from openvswitch to ovn, I've been troubled by this
  matter for a long time.

  ok, my scenario: I applied a subnets from ISP provider, let's call it
  subnet1 of public_network , After a period of time, the subnet IP is
  not enough, So I applied for another subnets, let's call it subnet2 of
  public_network. until now, the public_network will have two subnet.

  But FIPs based on two subnets cannot communicate with each other, The
  FIP of the subnet2 cannot communicate with itself either.

  I found some bug reports :
  <https://bugzilla.redhat.com/show_bug.cgi?id=1920025><https://access.redhat.com/errata/RHBA-2022:9044>
  <https://bugzilla.redhat.com/show_bug.cgi?id=1929901> , but those
  think it's a ovn bug.

  And in my test, I' found it's a neutron logical bug, yes or no, it's a
  bug, ha

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2058433/+subscriptions