[ovs-dev] [PATCH] ovn-controller: Don't bind non-existent interfaces.

Guru Shetty guru at ovn.org
Fri Mar 10 18:33:44 UTC 2017


On 8 March 2017 at 09:42, Russell Bryant <russell at ovn.org> wrote:

> On Wed, Mar 8, 2017 at 2:18 AM, Gurucharan Shetty <guru at ovn.org> wrote:
> > There are multiple reasons why a interface can exist
> > in the Open vSwitch database but not exist in the system.
> > For e.g, a restart of a host after a system crash. Ideally,
> > whoever added the interface in the Open vSwitch database
> > should remove those interfaces. But that usually does not
> > happen in practise. Based on experience, I have observerd
>
> practice and observed
>
> > that on any long lasting OVS installation there are always
> > a couple of stale interfaces.
> >
> > When a stale interface remains in the Open vSwitch database
> > and the container/VM initially backing that stale interface
> > is moved to a different machine, the two ovn-controllers
> > start over-writing the OVN-SB's port_binding table in a loop.
> >
> > This situation can be avoided, if ovn-controller only binds
> > the interfaces that actually have a valid 'ofport'.
> >
> > Signed-off-by: Gurucharan Shetty <guru at ovn.org>
>
> This sounds reasonable to me.
>
> Acked-by: Russell Bryant <russell at ovn.org>
>
Thanks. I applied this to master and 2.7


More information about the dev mailing list