On Tue, 20 Mar 2018 16:59:42 +0530 nusid...@redhat.com wrote: > From: Numan Siddique <nusid...@redhat.com> > > When a Logical_Switch_Port P's options is set with 'requested-chassis=hv1' > and if the user has bound this logical port to two OVS interfaces each in > different host (eg. hv1 and hv2), then ovn-controller in hv1 sets the > P's Port_Binding.chassis to hv1 which is as expected. But on hv2, > ovn-controller > is adding OF flows in table 0 and table 65 for the OVS interface instead of > considering 'P' as a remote port. When another logical port bound on hv2, > pings to the logical port 'P', the packet gets delivered to hv2 OVS interface > instead of hv1 OVS interface, which is wrong. > > This scenario is most likely to happen when requested-chassis option is used > by CMS during migration of a VM from one chassis to another. > > This patch fixes this issue by checking the Port_Binding's "requested-chassis" > option in physical.c before adding the flows in table 0 an 65. > > Reported-by: Marcin Mirecki <mmire...@redhat.com> > Reported-at: > https://mail.openvswitch.org/pipermail/ovs-dev/2018-March/345266.html > Signed-off-by: Numan Siddique <nusid...@redhat.com> > Tested-by: Marcin Mirecki <mmire...@redhat.com> > --- > > v2 -> v3: Addressed the review comment from Jakub Sitnicki > v1 -> v2: Updated the commit message > > ovn/controller/physical.c | 11 +++++++++++ > tests/ovn.at | 32 +++++++++++++++++++++++++++----- > 2 files changed, 38 insertions(+), 5 deletions(-)
Reviewed-by: Jakub Sitnicki <j...@redhat.com> _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
