Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 916728

Summary: [ovirt-engine-backend] Upgrade from 3.1 to 3.2 fails
Product: Red Hat Enterprise Virtualization Manager Reporter: Kiril Nesenko <knesenko>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED ERRATA QA Contact: Jiri Belka <jbelka>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.2.0CC: acathrow, cboyle, dfediuck, dyasny, eedri, iheim, lpeer, mgoldboi, Rhev-m-bugs, vvyazmin, yeylon, ykaul, yzaslavs
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: sf10 Doc Type: Bug Fix
Doc Text:
--no doc text required
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-10 21:34:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 922807    
Attachments:
Description Flags
logs none

Description Kiril Nesenko 2013-02-28 19:21:41 UTC
Created attachment 703936 [details]
logs

Description of problem:
Upgrade from 3.1 to 3.2 fails

2013-02-28 20:22:30::DEBUG::common_utils::474::root:: stderr = psql:drop_old_uuid_functions.sql:25: ERROR:  must be owner of function uuid_nil
CONTEXT:  SQL statement "drop function if exists uuid_nil()"
PL/pgSQL function "__temp_drop_old_uuid_functions" line 9 at SQL statement
psql:create_functions.sql:670: ERROR:  must be owner of function uuid_generate_v1

2013-02-28 20:22:30::DEBUG::common_utils::475::root:: retcode = 3
2013-02-28 20:22:30::ERROR::rhevm-upgrade::1181::root:: Traceback (most recent call last):
  File "/usr/bin/rhevm-upgrade", line 1168, in main
    runFunc([db.update], MSG_INFO_DB_UPDATE)
  File "/usr/bin/rhevm-upgrade", line 600, in runFunc
    func()
  File "/usr/bin/rhevm-upgrade", line 419, 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 478, in execCmd
    raise Exception(msg)
Exception: Error: Database update failed


Version-Release number of selected component (if applicable):
sf9

How reproducible:
Always

Steps to Reproduce:
1. Upgrade from 3.1 to sf9
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Eli Mesika 2013-03-01 00:24:28 UTC
please specify PG version

Comment 2 Eli Mesika 2013-03-01 07:30:59 UTC
(In reply to comment #1)
> please specify PG version

Tested both 

on PG 8.4.13 upgrade from 3.1.3 to 3.2 worked smoothly 

on PG 9.1.7 I got the following error during the upgrade:

>
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()"

This error is different from the reported one.
I will fix this error and attach to this BZ , however, I need an environment that reproduces the reported error

Comment 3 Eli Mesika 2013-03-01 08:05:12 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > please specify PG version
> 
> Tested both 
> 
> on PG 8.4.13 upgrade from 3.1.3 to 3.2 worked smoothly 

Succeeded to reproduce after using user engine instead of postgres

> 
> on PG 9.1.7 I got the following error during the upgrade:
> 
> >
> 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()"
> 
> This error is different from the reported one.
> I will fix this error and attach to this BZ , however, I need an environment
> that reproduces the reported error

Comment 4 Moran Goldboim 2013-03-10 23:13:13 UTC
*** Bug 919845 has been marked as a duplicate of this bug. ***

Comment 5 Jiri Belka 2013-03-12 15:36:35 UTC
OK, sf10 but there's different issue related to upgrade with rhevm-doc (BZ920678), so I did rpm --nodeps -Uhv rhevm-doc-3.2.0-0.2.beta.el6eng.noarch.rpm and the rest was OK.

Comment 6 Cheryn Tan 2013-04-03 06:52:02 UTC
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 7 errata-xmlrpc 2013-06-10 21:34:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0888.html