Bug 1323826

Summary: engine-setup stage 'Setup validation' takes too long to complete
Product: Red Hat Enterprise Virtualization Manager Reporter: Javier Coscia <jcoscia>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED ERRATA QA Contact: Aleksei Slaikovskii <aslaikov>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.7CC: didi, ekin.meroglu, emesika, gklein, jcoscia, lsurette, lsvaty, mgoldboi, mperina, oourfali, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, ykaul
Target Milestone: ovirt-4.0.0-alphaKeywords: ZStream
Target Release: 4.0.0   
Hardware: All   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1324733 (view as bug list) Environment:
Last Closed: 2016-08-23 20:34:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1324733    

Description Javier Coscia 2016-04-04 20:38:50 UTC 
Description of problem:

The stage 'Setup validation' takes long time to complete while upgrading from 
3.5.7 to 3.5.8. More than 7 hours

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

rhevm-3.5.7-0.1.el6ev.noarch == > rhevm-3.5.8-0.1.el6ev.noarch

How reproducible:

Happened in customer environment while upgrading to latest 3.5.x minor version

Steps to Reproduce:
1. Existing RHEV environment in 3.5.7
2. yum update rhevm-setup
3. engine-setup

Actual results:

Upgrade procedure took more than 7 hours to complete. Most of that time was in
/usr/share/ovirt-engine/setup/dbutils/validatedb.sh script

Expected results:

Upgrade shouldn't take that long

Additional info:

Will upload setup logs
Comment 19 Aleksei Slaikovskii 2016-08-05 16:46:01 UTC 
Everything went smooth in upgrading 4.0.0-9 to 4.0.2.3-0.1 except this fact that you need upgrade not only ovirt-engine-setup but also ovirt-engine-dwh-setup. Also in https://gerrit.ovirt.org/#/c/55724/ is mentioned that patch was validated on the customer problematic DB and solved the problem.
Comment 21 errata-xmlrpc 2016-08-23 20:34:15 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.

https://rhn.redhat.com/errata/RHEA-2016-1743.html