Handle rollbacks of DF DB failures in DF Neutron plugin

Bug #1497676 reported by Gal Sagie on 2015-09-20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Gal Sagie

Bug Description

Dragonflow plugin handles two DB's the remote NB API DB and the Neutron DB.
Some actions might fail at the NB DB but not the Neutron DB and vice versa, leaving the systems in an un-synchronized

Need to create a rollback mechanism for these cases or add a synchronization mechanism that alerts
on cases of differences between the two DB's

Gal Sagie (gal-sagie) on 2015-09-20
Changed in dragonflow:
importance: Undecided → Critical
assignee: nobody → Gal Sagie (gal-sagie)
Changed in dragonflow:
importance: Critical → Medium

Reviewed: https://review.openstack.org/282290
Committed: https://git.openstack.org/cgit/openstack/dragonflow/commit/?id=3b92dc8eac33ad96b6cd40ad80427c9951444d99
Submitter: Jenkins
Branch: master

commit 3b92dc8eac33ad96b6cd40ad80427c9951444d99
Author: Li Ma <email address hidden>
Date: Thu Feb 18 10:30:42 2016 +0800

    Implement DB consistency

    It is a distributed lock based on SQL. Each lock is
    associated with a Neutron project(tenant) and a given
    API session. It ensures that a lock is acquired and
    released in the same API context.

    The detailed description is in the spec review.

    Closes-Bug: #1529812
    Closes-Bug: #1529326
    Closes-Bug: #1497676
    Related-Bug: #1527234
    Implements: blueprint bp/keep-db-consistency

    Change-Id: Iff916481282f2d60df66c0e916f3045f9944531e

Changed in dragonflow:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers