Downgrade V20 should delete tables in configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
In Progress
|
Low
|
Simon Chang |
Bug Description
the v20 migration in trove/db/
This has the following consequences:
- Exceptions in initially creating the tables/columns/etc will be ignored causing the upgrade migration to fail, yet the migration will continue with silent errors
- Exceptions in subsequent upgrades may fail for other errors that generate the same exceptions
- Errors caused by code in future versions that corrupt the data in the tables will not be cleared during the downgrade/upgrade process, effectively leaving the user in an unrecoverable state
- The configuration data left in the tables may have business relationships to data in other tables which are cleared during their downgrade, thus invalidating the retained data
For these reasons, the downgrade should drop the appropriate tables and the exception catching should be removed from the update method.
Changed in trove: | |
assignee: | nobody → Simon Chang (changsimon) |
Changed in trove: | |
milestone: | none → juno-rc1 |
importance: | Undecided → Low |
Fix proposed to branch: master /review. openstack. org/117048
Review: https:/