Bug 1226942 - error upgrading db from 3.5 to 3.6 because null value in column "option_value"
Summary: error upgrading db from 3.5 to 3.6 because null value in column "option_value"
Keywords:
Status: CLOSED DUPLICATE of bug 1226944
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-01 13:38 UTC by Sharon Naftaly
Modified: 2016-09-20 03:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-02 06:31:16 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sharon Naftaly 2015-06-01 13:38:41 UTC
Description of problem:
When upgrading a customer's db from 3.5 to 3.6, using the schema.sh script found in ovirt-engine repo, it fails in the last post upgrade script. The error is:
0030_set_default_cluster_for_registration.sql:4: ERROR:  null value in column "option_value" violates not-null constraint

The reason is that the following query return null into option_value, since the value in the name column is not 'Default':
set option_value = (select vds_group_id from vds_groups where name ilike 'Default')

How reproducible:
run the schema.sh script on a db that returns null for the query:
select vds_group_id from vds_groups where name ilike 'Default'


Actual results:
failure in upgrading the database

Expected results:


Additional info:

Comment 1 Sharon Naftaly 2015-06-02 06:31:16 UTC

*** This bug has been marked as a duplicate of bug 1226944 ***


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