congress

DB operations failure with MySQL

Bug #1629988 reported by Tim Hinrichs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
congress
Fix Released
Critical
Unassigned
congress newton-rc3

Bug Description

Sharing the same db session means if another db operation takes
place during the transaction before an unlock takes place
(synchronizer or another request being served), MySQL complains and
fails to unlock table (because MySQL requires that all tables used
by the session holding a lock must also be locked). This causing all
subsequent db operations to fail.

By using a separate, one-time facade and session for add_policy,
this problem is resolved.

Tim Hinrichs (thinrichs)
Changed in congress:
status: New → In Progress
importance: Undecided → Critical
milestone: none → newton-rc3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to congress (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/381283

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on congress (stable/newton)

Change abandoned by Tim Hinrichs (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/381283

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

Reviewed: https://review.openstack.org/380684
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=c01c830829e29ce7725ed60045b09b66e632e660
Submitter: Jenkins
Branch: master

commit c01c830829e29ce7725ed60045b09b66e632e660
Author: Eric K <email address hidden>
Date: Fri Sep 30 19:38:42 2016 -0700

    Critical newton fix: Use new db session for table locking

    Sharing the same db session means if another db operation takes
    place during the transaction before an unlock takes place
    (synchronizer or another request being served), MySQL complains and
    fails to unlock table (because MySQL requires that all tables used
    by the session holding a lock must also be locked). This causing all
    subsequent db operations to fail.

    By using a separate, one-time facade and session for add_policy,
    this problem is resolved.

    Closes-bug: #1629988
    Change-Id: I73975aa6362431cb686851a42c70d70712cfb46b

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

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/381335

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/congress 4.0.0.0rc3

This issue was fixed in the openstack/congress 4.0.0.0rc3 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/congress 4.0.0

This issue was fixed in the openstack/congress 4.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/congress 5.0.0.0b1

This issue was fixed in the openstack/congress 5.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/congress 4.0.0

This issue was fixed in the openstack/congress 4.0.0 release.

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.