(previous description of this BZ was moved to BZ2019938 as per DFG decision) This bug is now just used to track BZ2018365 in OSP. The explanation for the other issue is still available at BZ2019938.
*** Bug 2018980 has been marked as a duplicate of this bug. ***
@ekuris is this the corresponding OSP tracking bug for BZ2017424? If so we need a blocker request on this one.
(In reply to Karrar Fida from comment #2) > @ekuris is this the corresponding OSP tracking bug for BZ2017424? > If so we need a blocker request on this one. Yes it is
By some cases I mean this - If a neutron router is connected to a provider network 'A' and private geneve networks. If the mtu of private networks (1442 in normal cases) is lesser than that of provider network (1500), then there is no need for neutron ml2ovn to set options:gateway_mtu=1500 even if the config option to enable gateway mtu is set.
After a debug session with Numan I am removing the blocker bug. This issue probably was in our product but we started to see it after a new patch was added in core ovn that expose the problem. The issue is important to be fixed because its impacts external connectivity
Hi Eran! We also think this should be fixed in OSP, but we moved that to BZ2019938 in order to leave this bug as a tracked for the initial FDP bug. Therefore I'm setting the TestOnly keyword again. Please answer back if I'm missing something!
*** Bug 2017424 has been marked as a duplicate of this bug. ***