[ovs-git] Open vSwitch: ovs-xapi-sync: Always set iface-id, not just when xs-vif-uuid changes. (branch-1.4)

dev at openvswitch.org dev at openvswitch.org
Fri Feb 10 16:43:23 UTC 2012

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Open vSwitch".

The branch, branch-1.4 has been updated
       via  d6af7b1021aef1be45508e63187f137a8cff5ac0 (commit)
      from  913aa4e441735f3a1e26752f1b6a711823b68848 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d6af7b1021aef1be45508e63187f137a8cff5ac0
Diffs: http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=d6af7b1021aef1be45508e63187f137a8cff5ac0
Author: Ben Pfaff <blp at nicira.com>
ovs-xapi-sync: Always set iface-id, not just when xs-vif-uuid changes.
When XAPI moves an interface from one bridge to another, the vif script
removes the vif from one bridge and adds it to (possibly) a different
bridge in a single transaction.  The new record does not have an iface-id
initially (because the vif script never adds the iface-id initially) but
it has the same name and xs-vif-uuid as the old one, so the caching logic
in ovs-xapi-sync failed to add a new iface-id.  This commit fixes the
caching logic.

Observed on XenServer 5.6.100.  It's possible that XAPI behavior changed in
later versions so the bug cannot be triggered there, but we have not

Bug #9414.
Reported-by: Duffie Cooley <dcooley at nicira.com>
Signed-off-by: Ben Pfaff <blp at nicira.com>


Summary of changes:
 .../usr_share_openvswitch_scripts_ovs-xapi-sync    |   31 ++++++++++---------
 1 files changed, 16 insertions(+), 15 deletions(-)

Open vSwitch

More information about the git mailing list