Migration 009, 010, 020 downgrade failures do not raise exceptions
Bug #1227881 reported by
Eric Harney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Rushi Agrawal |
Bug Description
009_add_
Looking at the other migration scripts (008, 015, etc.), I suspect we want these to raise an exception upon failure.
Changed in cinder: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in cinder: | |
assignee: | nobody → Rushi Agrawal (rushiagr) |
Changed in cinder: | |
status: | Confirmed → In Progress |
Changed in cinder: | |
milestone: | none → icehouse-1 |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/58442 github. com/openstack/ cinder/ commit/ 3ddf4511596b2fc fc4ec134cd9edae aba823e42b
Committed: http://
Submitter: Jenkins
Branch: master
commit 3ddf4511596b2fc fc4ec134cd9edae aba823e42b
Author: Rushi Agrawal <email address hidden>
Date: Tue Nov 26 11:48:38 2013 +0530
Fix suppressed exceptions for migration downgrade
In SQLAlchemy migration versions 009, 010 and 020, we missed
reraising exceptions while logging errors in case of a downgrade.
We don't want exceptions to pass silently. This patch fixes that.
Closes-bug: 1227881
Change-Id: Id11b1c5d2e26d2 08e88bb84e5b46c 4b7affc3f9f