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

Bug 1221309

Summary: [New] - ovirt engine update fails when default cluster is deleted.
Product: [Retired] oVirt Reporter: RamaKasturi <knarra>
Component: ovirt-engine-webadminAssignee: Eli Mesika <emesika>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6CC: ecohen, gklein, lsurette, mgoldboi, oourfali, rbalakri, sabose, yeylon
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-16 14:02:08 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:

Description RamaKasturi 2015-05-13 16:51:15 UTC
Description of problem:
ovirt engine update fails when default cluster is deleted.

Version-Release number of selected component (if applicable):
ovirt-engine-3.6.0-0.0.master.20150429182702.git939c2e8.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Delete the default cluster from the ovirt engine.
2. create a new cluster and add hosts to it.
3. Now try updating ovirt-engine by running the command yum update , followed by engine-setup.

Actual results:
engine setup fails.

Expected results:
Engine setup should not fail.

Additional info:

Comment 1 RamaKasturi 2015-05-13 16:53:35 UTC
Logs from install log :

psql:/usr/share/ovirt-engine/dbscripts/upgrade/post_upgrade/0030_set_default_cluster_for_registration.sql:4: ERROR:  null value in column "option_value" violates not-null constraint

Comment 2 RamaKasturi 2015-05-14 05:39:54 UTC
Logs can be found in the link below.
http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1221309/

Comment 3 Eli Mesika 2015-06-16 14:02:08 UTC

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