yahoo-eng-team team mailing list archive

[Terry Wilson <1341020@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

OVSBridge.add_port() runs ovs-vsctl to add the port, then runs ovs-vsctl
again to query the ofport of the newly created port. The ofport gets
assigned outside of any kind of transaction, and the OVS api defines an
empty set response([]) to mean that the ofport assignment is still
pending and a response of '-1' to mean that there is a failure.

The current get_port_ofport code treats these responses both as failures
even though '[]' will most likely later succeed. We need to implement a
retry mechanism to ensure that we don't incorrectly fail port creation.
Raising an exception on retry expiration also seems like a good idea.

** Affects: neutron
     Importance: Undecided
     Assignee: Terry Wilson (otherwiseguy)
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1341020

Title:
  after add_port, get_port_ofport may be called before vswitchd has
  assigned the ofport

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  OVSBridge.add_port() runs ovs-vsctl to add the port, then runs ovs-
  vsctl again to query the ofport of the newly created port. The ofport
  gets assigned outside of any kind of transaction, and the OVS api
  defines an empty set response([]) to mean that the ofport assignment
  is still pending and a response of '-1' to mean that there is a
  failure.

  The current get_port_ofport code treats these responses both as
  failures even though '[]' will most likely later succeed. We need to
  implement a retry mechanism to ensure that we don't incorrectly fail
  port creation. Raising an exception on retry expiration also seems
  like a good idea.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1341020/+subscriptions