Hide Forgot
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
(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
Moving target release to 3.3.2 since it's not fixed in 3.3.1 and not considered blocking.
rc build done, moving to ON_QA, packages will be available on updates-testing repository.
oVirt 3.3.2 has been released resolving the problem described in this bug report.