Bug 915925

Summary: Move fkvalidator.sh to tools/dbutils
Product: Red Hat Enterprise Virtualization Manager Reporter: Idith Tal-Kohen <italkohe>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact:
Priority: high    
Version: 3.2.0CC: acathrow, cpelland, dyasny, emesika, iheim, jbiddle, lpeer, mgoldboi, pstehlik, Rhev-m-bugs, yeylon, ykaul, yzaslavs
Target Milestone: ---Keywords: ZStream
Target Release: 3.1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the script fkvalidator.sh was stored in dbscripts, which did not activate until after the pre-upgrade process, even though it was required before the pre-upgrade. Now, a common.sh script has been created that stores commonly used environment settings and fixes multiple issues including the fkvalidator.sh issue.
Story Points: ---
Clone Of: 912305 Environment:
Last Closed: 2013-03-12 14:32:06 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: 912305    
Bug Blocks: 893459    

Comment 3 Ilanit Stein 2013-03-04 13:23:53 UTC
Alex, 

As this bug depends on bug 893459 fix/backport, in order to be verified
Can we change it's status please?

Comment 4 Yair Zaslavsky 2013-03-04 16:14:26 UTC
The complete commit message includes - 

Creating a common.sh for common environment settings of all tools.

What matters in this bug, and the fact it was inserted to 3.1.3 is the above part - the creation of common.sh script and usage of it in taskcleaner.sh

This is a code change, although it can be easily be browsed by looking for common.sh and looing at taskcleaner.sh

Comment 5 Ilanit Stein 2013-03-06 13:05:42 UTC
Thanks for the explanation. Verified on si-27.3

Comment 7 errata-xmlrpc 2013-03-12 14:32:06 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/RHBA-2013-0557.html