Description of problem: When running 'engine-backup.sh --mode=restore --file=file1', and the credentials kept in file1 do not work, it fails with "FATAL: Can't connect to the database". Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. engine-setup 2. engine-backup.sh --mode=backup --file-file1 3. engine-cleanup 4. initdb 5. engine-backup.sh --mode=restore --file=file1 Actual results: "FATAL: Can't connect to the database" Expected results: A message should be output helping the user setup a database with the credentials kept in the backup file. Additional info: In principle, engine-backup.sh could have done this by itself if the database was local, but this is non-trivial, already done by engine-setup, and will not be easy to replicate to this script without a complete rewrite (which might be done one day). It can't be done if the database is remote.
A solution was introduced during the review process for bug #1020277 (http://gerrit.ovirt.org/20264) but it was requested that it be separated out. Hence this bug.
Well, https://bugzilla.redhat.com/1002401 is already covering this issue, isn't it?
(In reply to Ofer Schreiber from comment #2) > Well, https://bugzilla.redhat.com/1002401 is already covering this issue, > isn't it? Yes. Eventually I just added stuff to usage().
*** This bug has been marked as a duplicate of bug 1002401 ***