neutron

BSN: inconsistency when backend missing during delete

Bug #1377350 reported by Kevin Benton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
Kevin Benton
neutron 2015.1.0 "kilo"
Icehouse
Fix Released
Undecided
Unassigned
neutron 2014.1.4
Juno
Fix Released
Undecided
Unassigned
neutron 2014.2.1

Bug Description

When objects are deleted in ML2 and there is a failure in a driver in post-commit. There is no retry mechanism to delete that object from with the driver at a later time.[1] This means that objects deleted while there is no connectivity to the backend controller will never be deleted until another even causes a synchronization.

1. https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L1039

Kevin Benton (kevinbenton)
Changed in neutron:
assignee: nobody → Kevin Benton (kevinbenton)
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/126102

Changed in neutron:
status: New → In Progress
Kyle Mestery (mestery)
Changed in neutron:
milestone: none → kilo-1
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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

commit e9f001a63a555f067c4567a88613d14853442524
Author: Kevin Benton <email address hidden>
Date: Thu Oct 2 11:26:50 2014 -0700

    BSN: Set inconsistency record on delete failure

    Set a bad value in the consistency DB on a delete
    failure so a sync is triggered the next time the backend
    servers become available.

    This fixes the issue where the backend servers are unavailable
    when an object is deleted from ML2 but not deleted from the
    backend.

    Closes-Bug: #1377350
    Change-Id: I24713a03af4d3499645241f900de1f572689c235

Changed in neutron:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/juno)

Fix proposed to branch: stable/juno
Review: https://review.openstack.org/135508

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/icehouse)

Fix proposed to branch: stable/icehouse
Review: https://review.openstack.org/135509

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

Reviewed: https://review.openstack.org/135508
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=ba647cae2932cda338441bc1f47e0668bba6b555
Submitter: Jenkins
Branch: stable/juno

commit ba647cae2932cda338441bc1f47e0668bba6b555
Author: Kevin Benton <email address hidden>
Date: Thu Oct 2 11:26:50 2014 -0700

    BSN: Set inconsistency record on delete failure

    Set a bad value in the consistency DB on a delete
    failure so a sync is triggered the next time the backend
    servers become available.

    This fixes the issue where the backend servers are unavailable
    when an object is deleted from ML2 but not deleted from the
    backend.

    Conflicts:
     neutron/tests/unit/bigswitch/test_servermanager.py

    Closes-Bug: #1377350
    Change-Id: I24713a03af4d3499645241f900de1f572689c235
    (cherry picked from commit e9f001a63a555f067c4567a88613d14853442524)

tags: added: in-stable-juno
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/icehouse)

Reviewed: https://review.openstack.org/135509
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0d599c6433a835fedd8460622df68f9e3adc36db
Submitter: Jenkins
Branch: stable/icehouse

commit 0d599c6433a835fedd8460622df68f9e3adc36db
Author: Kevin Benton <email address hidden>
Date: Thu Oct 2 11:26:50 2014 -0700

    BSN: Set inconsistency record on delete failure

    Set a bad value in the consistency DB on a delete
    failure so a sync is triggered the next time the backend
    servers become available.

    This fixes the issue where the backend servers are unavailable
    when an object is deleted from ML2 but not deleted from the
    backend.

    Conflicts:
     neutron/tests/unit/bigswitch/test_servermanager.py

    Closes-Bug: #1377350
    Change-Id: I24713a03af4d3499645241f900de1f572689c235
    (cherry picked from commit e9f001a63a555f067c4567a88613d14853442524)

tags: added: in-stable-icehouse
Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: kilo-1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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