yahoo-eng-team team mailing list archive

[OpenStack Infra <1649887@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/410780
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9bab88ba83a6f395cfec5d1351a1597c05fee607
Submitter: Jenkins
Branch:    master

commit 9bab88ba83a6f395cfec5d1351a1597c05fee607
Author: Armando Migliaccio <armamig@xxxxxxxxx>
Date:   Wed Dec 14 05:12:32 2016 -0800

    Account for unwire failures during OVS trunk rewiring operations
    
    If a failure occurs while unwiring stale ports, we currently
    ignore the outcome of the operation, whereas we should at least
    warn the user that something is not quite as it is supposed
    to be.
    
    This patch makes sure that trunk status is accurately reflected
    after a sequence of unwire+wire operations for a given trunk.
    
    Closes-bug: #1649887
    
    Change-Id: I3b6ed57e00c0146babe23ea6ed0ca14e83020d26


** Changed in: neutron
       Status: In Progress => 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/1649887

Title:
  failures during stale subports removal not reflected in trunk status

Status in neutron:
  Fix Released

Bug description:
  Noticed while looking at latest code [1] for OVS trunk driver. the
  status of the unwire operation is not accounted for.

  [1]
  https://github.com/openstack/neutron/blob/master/neutron/services/trunk/drivers/openvswitch/agent/ovsdb_handler.py#L387

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