Bug 1009899

Summary: exportDbSchema scripts generates output file with wrong name
Product: [Retired] oVirt Reporter: Sandro Bonazzola <sbonazzo>
Component: ovirt-engine-coreAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 3.3CC: acathrow, ecohen, iheim, yeylon
Target Milestone: ---   
Target Release: 3.3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-19 14:24:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Sandro Bonazzola 2013-09-19 13:08:51 UTC
Description of problem:
exportDbSchema scripts generates output file with wrong name

Version-Release number of selected component (if applicable):
ovirt-engine-dbscripts-3.4.0-0.2.master.20130918140615.git54da2f7.fc18.noarch

How reproducible:
100%

Steps to Reproduce:
1. /usr/share/ovirt-engine/dbscripts/exportDbSchema.sh -s localhost -d engine -u engine -v -l /tmp/log

Actual results:
-v doesn't trigger any verbosity and the ouptut is:
 Done.
 Exported file is .engine.select version from schema_version where current;
 03030890.schema.

The file created is:
"/usr/share/ovirt-engine/dbscripts/.engine.select version from schema_version where current;\n03030890.schema"


Expected results:
-v turn on verbosity or doesn't exist

 The output file created should be:
./usr/share/ovirt-engine/dbscripts/.engine.03030890.schema

Comment 1 Sandro Bonazzola 2013-09-19 13:28:32 UTC
(In reply to Sandro Bonazzola from comment #0)

> Actual results:
> -v doesn't trigger any verbosity and the ouptut is:
>  Done.
>  Exported file is .engine.select version from schema_version where current;
>  03030890.schema.
> 
> The file created is:
> "/usr/share/ovirt-engine/dbscripts/.engine.select version from
> schema_version where current;\n03030890.schema"

After further testing the wrong file naming is due to -v switch.


> Expected results:

-v turn on verbosity without causing wrong file naming

The output file created should be:
./usr/share/ovirt-engine/dbscripts/.engine.03030890.schema

Comment 2 Sandro Bonazzola 2013-11-06 16:02:34 UTC
Moving target release to 3.3.2 since it's not fixed in 3.3.1 and not considered blocking.

Comment 3 Sandro Bonazzola 2013-12-13 16:02:12 UTC
rc build done, moving to ON_QA, packages will be available on updates-testing repository.

Comment 4 Sandro Bonazzola 2013-12-19 14:24:50 UTC
oVirt 3.3.2 has been released resolving the problem described in this bug report.