yahoo-eng-team team mailing list archive

[OpenStack Infra <1523859@xxxxxxxxxxxxxxxxxx>]

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

commit cb8af9bd50659daca4c1dea4070a011190ef3461
Author: Sreekumar S <sreesiv@xxxxxxxxx>
Date:   Mon Jun 20 21:06:19 2016 +0530

    Fixes port device_id/device_owner change in failed operation
    
    If a router is a attached to a neutron port and that operation
    fails at a late stage in the processing then the 'device_id' and
    'device_owner' attributes of the port are still changed. The
    failed operation should not change them.
    
    The reason is, as of commit 0947458018725b241603139f4ec6f92e84b2f29b,
    the update of those attributes happens outside of the DB transaction.
    For failed operation, the values are not reset back to their original
    values.
    
    Change-Id: I797df266dafc41843408dc95a6ce9f986db5c21c
    Closes-Bug: #1523859


** 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/1523859

Title:
  Failing router interface add changes port device_id/device_owner
  attributes

Status in neutron:
  Fix Released

Bug description:
  If a router is a attached to a neutron port and that operation fails
  at a late stage in the processing then the 'device_id' and
  'device_owner' attributes of the port are still changed. The failed
  operation should not change them.

  The reason is that, as of commit
  0947458018725b241603139f4ec6f92e84b2f29b, the update of those
  attributes happens outside of the DB transaction.

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