The migration for scheduled jobs needs to drop the table first
Bug #1845482 reported by
Renat Akhmerov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Fix Released
|
Critical
|
Renat Akhmerov | ||
Bug Description
We have to check if the table already exists and drop it in the migration first, if needed. This is because the DB model for scheduled jobs was released w/o a migration in the first place, so for some users the table was created automatically at Mistral run based on the model. But the structure of the table is old so we need to recreate it anyway in this migration. It's safe to drop this table because it contains temporary data.
See https:/
| Changed in mistral: | |
| assignee: | nobody → Renat Akhmerov (rakhmerov) |
| milestone: | none → ussuri-rc1 |
| importance: | Undecided → Critical |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to mistral (master) | #1 |
| Changed in mistral: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to mistral (master) | #2 |
| Changed in mistral: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/mistral 9.0.0.0rc1 | #3 |
| Changed in mistral: | |
| milestone: | ussuri-rc1 → train-rc1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/