db missing the 'unique_key' column for delayed_calls_v2 table

Bug #1610269 reported by Ryan Hallisey on 2016-08-05
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mistral
Undecided
Michal Gershenzon

Bug Description

(pymysql.err.InternalError) (1054, u"Unknown column 'unique_key' in 'field list'")

The DB is missing the unique_key field as part of the delayed_calls_v2 table.

Dougal Matthews (d0ugal) on 2016-08-08
Changed in mistral:
status: New → Confirmed
Changed in mistral:
assignee: nobody → Michal Gershenzon (michal-gershenzon)

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

Changed in mistral:
status: Confirmed → In Progress

Reviewed: https://review.openstack.org/352376
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=8e221ddbd84b11364208fd505c9a7854aca1c854
Submitter: Jenkins
Branch: master

commit 8e221ddbd84b11364208fd505c9a7854aca1c854
Author: Michal Gershenzon <email address hidden>
Date: Mon Aug 8 11:57:11 2016 +0000

    Add unique keys for non locking model

    The unique key colums are part of the new non locking model.
    The migration scripts adds 2 unique key columns to 2 tables.

    One of the new columns is already in the model and the other is
    under review.

    Change-Id: Icd352ed709f378a8141bcf6264bc9abba0f8db9a
    Closes-Bug: #1610269

Changed in mistral:
status: In Progress → Fix Released

This issue was fixed in the openstack/mistral 3.0.0.0b3 development milestone.

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

Other bug subscribers