[Users] Fedora upgrading from 3.1 to 3.2
Karli Sjöberg
Karli.Sjoberg at slu.se
Mon Mar 11 11:35:29 UTC 2013
mån 2013-03-11 klockan 12:20 +0100 skrev Juan Hernandez:
On 03/11/2013 12:16 PM, Karli Sjöberg wrote:
> in the absence of any official path, we have started working out our own
> procedure for going from oVirt-3.1/Fedora 17 to oVirt-3.2/Fedora 18.
> We´ve come about halfway into upgrading to the engine node, where we
> have managed to get it up to 18, with postgres, httpd and
> ovirt-engine-3.1.0-4 running and functional. Then we edit our
> ovirt-engine.repo to add 3.2 packages, yum update ovirt-engine-setup,
> then run engine-upgrade, that fails on upgrading the database. The log
> file is attached. What could be the issue here?
The service is failing to start after the upgrade. Can you check
/var/log/messages? What about /var/log/ovirt-engine/{engine.log,server.log}?
Well that comes after failing to upgrade the database, engine- and server.log attached, doesn´t say anything useful really. It´s rather here it starts going south:
2013-03-11 11:56:49::DEBUG::engine-upgrade::412::root:: DB Update started
2013-03-11 11:56:49::DEBUG::common_utils::434::root:: Executing command --> '/usr/share/ovirt-engine/dbscripts/upgrade.sh -s localhost -p 5432 -u engine -d engine_2013_03_11_11_54_00'
2013-03-11 11:56: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-03-11 11:56:54::DEBUG::common_utils::473::root:: stderr = psql:common_sp.sql:524: NOTICE: drop cascades to function fn_db_get_async_tasks()
psql:common_sp.sql:567: NOTICE: type "fk_info_rs" does not exist, skipping
psql:drop_all_views.sql:1: NOTICE: drop cascades to 9 other objects
...
psql:common_sp.sql:524: NOTICE: drop cascades to function fn_db_get_async_tasks()
psql:drop_old_uuid_functions.sql:25: NOTICE: extension "uuid" does not exist, skipping
CONTEXT: SQL statement "DROP EXTENSION IF EXISTS uuid--ossp CASCADE;"
PL/pgSQL function __temp_drop_old_uuid_functions() line 6 at EXECUTE statement
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:379: WARNING: GLOBAL is deprecated in temporary table creation
LINE 25: CREATE GLOBAL TEMPORARY TABLE tt_TEMP22
^
psql:create_functions.sql:535: NOTICE: type "all_vds_group_usage_rs" does not exist, skipping
psql:create_functions.sql:570: NOTICE: type "all_storage_usage_rs" does not exist, skipping
psql:create_functions.sql:671: ERROR: must be owner of function uuid_generate_v1
2013-03-11 11:56:54::DEBUG::common_utils::474::root:: retcode = 3
2013-03-11 11:56:54::ERROR::engine-upgrade::1078::root:: Traceback (most recent call last):
File "/usr/bin/engine-upgrade", line 1065, in main
runFunc([db.update], MSG_INFO_DB_UPDATE)
File "/usr/bin/engine-upgrade", line 594, in runFunc
func()
File "/usr/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
...
/Karli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130311/f177aac0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: engine.log
Type: text/x-log
Size: 465039 bytes
Desc: engine.log
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130311/f177aac0/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: server.log
Type: text/x-log
Size: 27221 bytes
Desc: server.log
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130311/f177aac0/attachment-0003.bin>
More information about the Users
mailing list