Bug 906270 - Upgrade from 3.1 shows error in DB upgrade
Summary: Upgrade from 3.1 shows error in DB upgrade
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.2
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ---
: ---
Assignee: Alex Lourie
QA Contact:
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-31 10:37 UTC by Alex Lourie
Modified: 2013-07-16 06:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-16 06:42:25 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
upgrade log (113.19 KB, text/x-log)
2013-01-31 10:37 UTC, Alex Lourie
no flags Details
stdout of engine-upgrade (2.43 KB, text/plain)
2013-01-31 16:47 UTC, Sandro Bonazzola
no flags Details
output with a wrong password (2.24 KB, text/plain)
2013-02-05 09:34 UTC, Sandro Bonazzola
no flags Details
engine upgrade log with wrong password (138.75 KB, text/x-log)
2013-02-05 15:15 UTC, Sandro Bonazzola
no flags Details

Description Alex Lourie 2013-01-31 10:37:36 UTC
Created attachment 690841 [details]
upgrade log

Description of problem:

During the upgrade of the 3.1 installation on F17 to 3.2 on F18 there's a following error appears:

engine_2013_01_30_21_30_41'
2013-01-30 21:33:54::DEBUG::common_utils::472::root:: output = /usr/share/ovirt-engine/dbscripts /usr/share/ovirt-engine/dbscripts
upgrade script detected a change in Config, View or Stored Procedure...

2013-01-30 21:33:54::DEBUG::common_utils::473::root:: stderr = psql:drop_old_uuid_functions.sql:25: ERROR:  cannot drop function uuid_nil() because extension uuid-ossp requires it
HINT:  You can drop extension uuid-ossp instead.
CONTEXT:  SQL statement "drop function if exists  uuid_nil()"
PL/pgSQL function __temp_drop_old_uuid_functions() line 10 at SQL statement
psql:create_functions.sql:671: ERROR:  must be owner of function uuid_generate_v1

2013-01-30 21:33:54::DEBUG::common_utils::474::root:: retcode = 3
2013-01-30 21:33:54::ERROR::engine-upgrade::1078::root:: Traceback (most recent call last):
  File "/bin/engine-upgrade", line 1065, in main
    runFunc([db.update], MSG_INFO_DB_UPDATE)
  File "/bin/engine-upgrade", line 594, in runFunc
    func()
  File "/bin/engine-upgrade", line 429, in update
    output, rc = utils.execCmd(cmdList=cmd, failOnError=True, msg=MSG_ERROR_UPDATE_DB)
  File "/usr/share/ovirt-engine/scripts/common_utils.py", line 477, in execCmd
    raise Exception(msg)
Exception: Error: Database update failed

Comment 2 Sandro Bonazzola 2013-01-31 16:47:11 UTC
Created attachment 691079 [details]
stdout of engine-upgrade

engine-upgrade asks about 8 times the db password after the rpms upgrade. here is what I can see in the console.

Comment 3 Alex Lourie 2013-01-31 20:58:18 UTC
Sandro

Please attach the content of the /etc/ovirt-engine/.pgpass file?

Thanks.

Comment 4 Sandro Bonazzola 2013-02-01 07:18:06 UTC
Here is the content of /etc/ovirt-engine/.pgpass.
#####  oVirt-engine DB ADMIN settings section. Do not change!!
localhost:5432:*:postgres:qum5net
localhost:5432:engine:engine:qum5net
#####  End of oVirt-engine DB ADMIN settings section.

Comment 5 Alex Lourie 2013-02-03 09:34:10 UTC
Hi Sandro

Could you please try to reproduce the "password prompts" issue?

If you can, please enter wrong password. I need to see where it fails.

Thanks.

Comment 6 Sandro Bonazzola 2013-02-05 09:34:15 UTC
Created attachment 693289 [details]
output with a wrong password

As requested in comment #5, I can reproduce the password prompt issue.
I've used a wrong password after rpm update. Here is the output.
Do you need to retry using wrong password on other successive prompt?

Comment 7 Sandro Bonazzola 2013-02-05 15:15:45 UTC
Created attachment 693406 [details]
engine upgrade log with wrong password

Comment 8 Eli Mesika 2013-02-19 13:03:17 UTC
Alex, what is the status of this bug?

Comment 9 Alex Lourie 2013-03-07 09:56:29 UTC
We are still working on the upgrade actions.

Some configuration files need updating when upgrading from 3.1; that's a part way to solving this bug.

Comment 11 Alex Lourie 2013-07-02 11:58:39 UTC
@Karli

Please update us on your progress.

Thanks.

Comment 12 Itamar Heim 2013-07-16 06:42:25 UTC
closing on no feedback - please re-open if relevant


Note You need to log in before you can comment on or make changes to this bug.