Created attachment 600505 [details] logs Description of problem: Upgrade fails when dwh service is up. There are live connection to the DB. Version-Release number of selected component (if applicable): si12 How reproducible: Steps to Reproduce: 1. Try to run rhevm-update when dwh service is up. 2. 3. Actual results: update fails due to DB connections Expected results: Additional info:
Patch posted for review: http://gerrit.ovirt.org/#/c/7691/
Merged upstream: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=c5f777a45a04a1231ab08f1ea501ee8e25a1f2bc
Not Fixed, 3.1/si17 --> si18 1. I install si17 clean, with reports+dwh 2. I add in REPO the si18 url 3. I run yum update rhevm-setup & rhevm-upgrade Backing Up Database... [ DONE ] Rename Database... [ ERROR ] Error: Database rename failed. Check that there are no active connections to the DB and try again. Error: Upgrade failed. Not Fixed, 3.1/si17 --> si18 See attached, ------------------------------------------ 2012-09-19 08:01:30::ERROR::rhevm-upgrade::930::root:: Traceback (most recent call last): File "/usr/bin/rhevm-upgrade", line 923, in <module> main(options) File "/usr/bin/rhevm-upgrade", line 834, in main runFunc([[db.rename, DB_NAME_TEMP]], MSG_INFO_RENAME_DB) File "/usr/bin/rhevm-upgrade", line 595, in runFunc func[0](*func[1:]) File "/usr/bin/rhevm-upgrade", line 551, in rename utils.execRemoteSqlCommand(SERVER_ADMIN, SERVER_NAME, SERVER_PORT, basedefs.DB_TEMPLATE, query, True, MSG_ERROR_RENAME_DB) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 365, in execRemoteSqlCommand return execCmd(cmdList=cmd, failOnError=failOnError, msg=errMsg, envDict=env) File "/usr/share/ovirt-engine/scripts/common_utils.py", line 339, in execCmd raise Exception(msg) Exception: Error: Database rename failed. Check that there are no active connections to the DB and try again.
Created attachment 614200 [details] si17-si18
Why this bz moved to assigned ? The fix was to print a nice error message: Error: Database rename failed. Check that there are no active connections to the DB and try again. That what it does. David take a look on the patch fix.
Hi Kiril, Thanks now I see, what the fix is, but why doesnt upgrade handles the open connections to the DB, If a user wants to upgrade, Why should they do it manually ?
Waiting for ack on my replay and later on I will move it to verify.
Fixed, 3.1/si18 User should stop the DWH manually. (If not solving the issue - User should restart postgresql service in order to close open connections.) Fixed, 3.1/si18