From: "Lance Richardson" <lrichard@redhat.com> To: "Devin Acosta" <devin@pabstatencio.com> Cc: "Russell Bryant" <rbryant@redhat.com>, "Numan Siddique" <nusiddiq@redhat.com>, "Marcin Mirecki" <mmirecki@redhat.com>, "users" <Users@ovirt.org> Sent: Tuesday, December 20, 2016 4:50:53 PM Subject: Re: oVirt / OVN / MTU
From: "Devin Acosta" <devin@pabstatencio.com> To: "Russell Bryant" <rbryant@redhat.com> Cc: "Numan Siddique" <nusiddiq@redhat.com>, "Lance Richardson" <lrichard@redhat.com>, "Marcin Mirecki" <mmirecki@redhat.com>, "users" <Users@ovirt.org> Sent: Tuesday, December 20, 2016 4:38:32 PM Subject: Re: oVirt / OVN / MTU
So some port got stuck on a box? Any idea what would cause this and what i should do to remove it?
Maybe there's a better way, but you could run this on the two chassis that are involved:
ovs-vsctl --format table --columns=name,external-ids list Interface
And look for for port UUID from the log message, it should show up with "iface-id=" on both chassis (but should appear on only one).
Once you figure out which one is wrong, do:
ovs-vsctl remove Interface <port-name> external_ids iface-id=<interface-id>
If you're running a recent version of ovs master, you might just need the fix listed below which was committed yesterday (maybe you don't have a duplicate port binding after all): commit f90bb0909c5320c2421cce392ad0d4ffaecb98e7 Author: Mickey Spiegel <mickeys.dev@gmail.com> Date: Tue Dec 20 13:23:46 2016 -0800 ovn-controller: Log chassis claiming lport only when changes occur. With recent OVN commits, the logic for a chassis to claim or release a logical port was consolidated. This is a good thing. However, there was a logic change that resulted in VLOG_INFO being generated every time on the ovn-controller. This patch changes the logic so that VLOG_INFO is only generated when there is a change, for example when the chassis claims an lport the first time. Signed-off-by: Mickey Spiegel <mickeys.dev@gmail.com> Signed-off-by: Ben Pfaff <blp@ovn.org>