On Tue, Mar 20, 2018 at 04:59:42PM +0530, [email protected] wrote: > From: Numan Siddique <[email protected]> > > 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 <[email protected]> > Reported-at: > https://mail.openvswitch.org/pipermail/ovs-dev/2018-March/345266.html > Signed-off-by: Numan Siddique <[email protected]> > Tested-by: Marcin Mirecki <[email protected]>
Thank you. I applied this to master and branch-2.9. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
