Description of problem:
Not sure if having hardcoded db name is valid approach here:
# grep '^psql' /usr/share/ovirt-engine/dbscripts/engine-psql.sh
psql -U "${USERNAME}" -h "${HOST}" -p "${port}" engine "$@" | tee -a "${LOGFILE}" 2>&1
Version-Release number of selected component (if applicable):
redhat-support-plugin-rhev-3.6.0-15.el6.noarch
redhat-support-plugin-rhev-4.0.0-4.el7ev.noarch
How reproducible:
100%
Steps to Reproduce:
1. check if db name is a variable or hardcoded in shell script
2.
3.
Actual results:
db name is hardcoded
Expected results:
should be variable, let's imagine remote db
Additional info:
not tested against remote db, just checking a part of the code
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA
Description of problem: Not sure if having hardcoded db name is valid approach here: # grep '^psql' /usr/share/ovirt-engine/dbscripts/engine-psql.sh psql -U "${USERNAME}" -h "${HOST}" -p "${port}" engine "$@" | tee -a "${LOGFILE}" 2>&1 Version-Release number of selected component (if applicable): redhat-support-plugin-rhev-3.6.0-15.el6.noarch redhat-support-plugin-rhev-4.0.0-4.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. check if db name is a variable or hardcoded in shell script 2. 3. Actual results: db name is hardcoded Expected results: should be variable, let's imagine remote db Additional info: not tested against remote db, just checking a part of the code