bug in ipam_backend_mixin delete_port

Bug #1496554 reported by Aaron Rosen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
Aaron Rosen

Bug Description

It's possible for a port to be deleted concurrently in which case here:

https://github.com/openstack/neutron/blob/master/neutron/db/ipam_backend_mixin.py#L417

None will be passed to context.session.delete() This results in this error being raised:

http://logs.openstack.org/25/224225/2/check/gate-tempest-dsvm-networking-ovn/8719aa6/logs/screen-q-svc.txt.gz?level=TRACE#_2015-09-16_18_38_59_368

Aaron Rosen (arosen)
Changed in neutron:
assignee: nobody → Aaron Rosen (arosen)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/224289

Changed in neutron:
status: New → In Progress
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
Changed in neutron:
importance: Undecided → High
milestone: none → liberty-rc1
importance: High → Low
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

On closer inspection this looks like to be mostly exercised by the way OVN works

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to neutron (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/224337

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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

commit 77de4a3b54110c2d5b8b38efdfbeb5c35e2cb16d
Author: Aaron Rosen <email address hidden>
Date: Wed Sep 16 15:50:21 2015 -0700

    ipam: Prevent none from being passed to delete

    Previously, it was possible for None to be passed to context.session.delete()
    if a port was not found (usually a result of a concurrent delete). This
    resulted in an UnmappedInstanceError. This is avoided now by calling
    query.delete() directly which does not raise any exceptions.

    Change-Id: I3b9f513308d90874ac8e8a7f6345697978d4920f
    Closes-bug: #1496554

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: liberty-rc1 → 7.0.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/224337
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.