virnetdevbridge: Ignore EEXIST when adding an entry to fdb
virnetdevbridge: Ignore EEXIST when adding an entry to fdb

When updating entries in a bridge forwarding database (i.e., when
macTableManager='libvirt' is configured for the bridge), we may end up
in a situation when the entry we want to add is already present. Let's
just ignore the error in such a case.

This fixes an error to resume a domain when fdb entries were not
properly removed when the domain was paused:

    virsh # resume test
    error: Failed to resume domain test
    error: error adding fdb entry for vnet2: File exists

For some reason, fdb entries are only removed when libvirt explicitly
stops CPUs, but nothing happens when we just get STOP event from QEMU.
An alternative approach would be to make sure we always remove the
entries regardless on why a domain was paused (e.g., during migration),
but that would be a significantly more disruptive change with possible
side effects.

https://bugzilla.redhat.com/show_bug.cgi?id=1603155

Signed-off-by: Jiri Denemark <62bdf77dc47919a4d59a91822129d14633cfca81@redhat.com>
Reviewed-by: Laine Stump <c23361c43fbf79fed83e8b76173707b083d6caf5@redhat.com>

jfehlig/libvirt,jfehlig/libvirt,olafhering/libvirt,nertpinx/libvirt,crobinso/libvirt,crobinso/libvirt,libvirt/libvirt,crobinso/libvirt,nertpinx/libvirt,zippy2/libvirt,libvirt/libvirt,nertpinx/libvirt,crobinso/libvirt,jfehlig/libvirt,libvirt/libvirt,nertpinx/libvirt,libvirt/libvirt,nertpinx/libvirt,zippy2/libvirt,olafhering/libvirt,olafhering/libvirt,jfehlig/libvirt,olafhering/libvirt,zippy2/libvirt,zippy2/libvirt