← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1614059] Re: TrunkStub.trunk_deleted is called with NULL trunk object

 

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

commit c5629e9734f566aaf1692ed3ae016951a62bebe0
Author: Babu Shanmugam <bschanmu@xxxxxxxxxx>
Date:   Wed Aug 17 11:00:28 2016 +0000

    TrunkStub.trunk_deleted is called with NULL trunk object
    
    On AFTER_DELETE event, the trunk object is set in payload.original_trunk,
    but this is not used for calling TrunkStub.trunk_deleted(), instead it is
    called with payload.current_trunk which is 'None'.
    
    Closes-bug: #1614059
    Change-Id: Ib09516379ef5d48bf723a9ba098d90bf6bf5a0eb


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

Title:
  TrunkStub.trunk_deleted is called with NULL trunk object

Status in neutron:
  Fix Released

Bug description:
  On AFTER_DELETE event, the trunk object is set in
  payload.original_trunk, but this is not used for calling
  TrunkStub.trunk_deleted(), instead it is called with
  payload.current_trunk which is 'None'.

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


References