Red Hat Bugzilla – Bug 880067
[rhevm-upgrade] pre-upgrade checks should check if DB is up-gradable before starting the process
Last modified: 2015-09-22 09:09 EDT
Description of problem:
in our pre-upgrade tests we must check if data-base is upgradable before we start the process and alert the user, upgrade is of the complex scenarios and might fail on different places, once it fails, its pretty frustrating asking the user to manually revert its setup (install jboss again, rhevm, run setup, drop-db, import db, rename..).
I suggest that during our pre-upgrade checks, we will try to upgrade the db, if we fail, we should fail the upgrade process (no harm done to the existing env), alerting the user to call support, they will make needed changes in the data-base, and user will try again, now with higher chances for success.
i agree a pre-upgraed test on the db is of value (actually thought we had it in the past)
3.3 Includes a major re-write of ovirt-engine-setup (which is responsible for upgrade as well now).
This re-write makes this bug obsolete, as the upgrade supports now real transactions for every aspect of the upgrade, and the DB upgrade is done at early stage.
Therefore, I'm closing this bug as it is already included in 3.3 upstream. Thanks for the bug, and hope you'll find the new implementation helpful.