Bug 964197

Summary: fkvalidator.sh - some args are not honoured
Product: Red Hat Enterprise Virtualization Manager Reporter: Pavel Stehlik <pstehlik>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, bazulay, cpelland, iheim, jkt, lpeer, pstehlik, Rhev-m-bugs, yeylon, yzaslavs
Target Milestone: ---Keywords: ZStream
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: is7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 986922 (view as bug list) Environment:
Last Closed: 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: 986922    

Description Pavel Stehlik 2013-05-17 13:56:01 UTC 
Description of problem:
 fkvalidator.sh doesn't respect arguments (-v -l) eg:
 "/usr/share/ovirt-engine/scripts/dbutils/fkvalidator.sh -s localhost -d engine -u engine -l /tmp/fk.log -v" shows output: 
"Constraint violation found in  step (job_id)".

The constraint violation is correct, however no verbose log nor log file is created. Same bahaviour in standalone usage of those 2 args.

Version-Release number of selected component (if applicable):
rhevm-setup-3.2.0-10.26.rc.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. see https://bugzilla.redhat.com/show_bug.cgi?id=893459#c0
2.
3.
  
Actual results:


Expected results:
I'd expect to see whole record(s) from DB (at least in case of '-v') as this can indicate some more troubles in system. 
Also log file should be created & should contain an output.

Additional info:
logfile is not even created by using simple '-l' (without any optional path/filename).
Comment 3 Eli Mesika 2013-06-24 09:02:54 UTC 
Pavel , a simple and quick solution is to add for each violation the query syntax of how to get the violated records.

This will be added in teh case that -v is used

Example :

Constraint violation found in  event_subscriber (event_up_name) 
Query : select event_up_name from event_subscriber where event_up_name not in (select event_up_name  from event_map);

This query can be copied and run by psql to get the violated records.

Is that acceptabe ???
Comment 6 Eli Mesika 2013-07-22 13:02:24 UTC 
fixed in commit: 5a1c143
Comment 8 Itamar Heim 2014-01-21 22:32:44 UTC 
Closing - RHEV 3.3 Released
Comment 9 Itamar Heim 2014-01-21 22:32:49 UTC 
Closing - RHEV 3.3 Released