cloudstack
cloudstack copied to clipboard
CloudStack DB upgrade failure causes upgrade mess
If CloudStack is being upgraded and a DB issue is hit (say table is already altered, forgot to have systemvmtemplate in the deb/rpm build etc), then the whole transaction isn't reverted maybe partially. This causes changes to persist, changes such as new tables being added, existing tables/views altered. As an operator, I would prefer CloudStack to revert its DB changes when an DB upgrade path issue is hit.
ISSUE TYPE
- Bug Report
COMPONENT NAME
DB, Upgrades