yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

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

Title:
  cannot distinguish error from no port in ovs_lib list operation

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  list operations in ovs_lib returns an empty list even if Runtime Error occurs.
  As a result, when Runtime Error occurs, a caller thinks all ovs ports have disappeared.
  ovs-vsctl sometimes fails (mostly raises alarm error?)
  ovs_lib should provide a way to distinguish these two situations.

  list operations in ovs_lib
  - get_vif_port_set (used by OVS agent and ryu agent)
  - get_vif_ports (used by NEC agent, OVS cleanup)
  - get_bridge (used by OVS agent, OVS cleanup)

  It affects all agent using the above list operation.

  It affects OVS agent and NEC agent. It triggers unexpected port
  deletions.

  In OVS cleanup, there is no negative effect. It just nothing for this
  case.

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