Bug 1073372
| Summary: | Restore doesn't work after cleanup | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Lior Vernia <lvernia> |
| Component: | ovirt-engine-installer | Assignee: | Yedidyah Bar David <didi> |
| Status: | CLOSED DUPLICATE | QA Contact: | Pavel Stehlik <pstehlik> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.4 | CC: | acathrow, bazulay, didi, gklein, iheim, sbonazzo, yeylon |
| Target Milestone: | --- | ||
| Target Release: | 3.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-03-09 10:04:10 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: | |
| Embargoed: | |||
Also, this was on CentOS 6.5. Dropping and creating the database (on the same machine at least) does work. Didi, can we fix this for 3.4.0? (In reply to Lior Vernia from comment #0) > Description of problem: > > Running engine-backup (in restore mode), following an engine-cleanup, > results in the following error: "FATAL: Database is not empty" Closing as duplicate of bug #1066654 "engine-cleanup does not cleanup everything". > > > Version-Release number of selected component (if applicable): > > oVirt 3.4.0 RC. > > > How reproducible: > > Always (well, one out of one for me). > > > Steps to Reproduce: > 1. Run "engine-setup". > 2. Configure all sorts of things on engine. > 3. Run "engine-backup --mode=backup --file=ovirt.backup --log=ovirt.log" > 4. Run "engine-cleanup". > 5. Run "engine-backup --mode=restore --file=ovirt.backup --log=ovirt.log" > > Actual results: > > Get the aforementioned error. > > > Expected results: > > The deployment is restored. > > > Additional info: > > Log file looks like this: > > > 2014-03-06 04:50:18 18401: Backing up... > 2014-03-06 04:50:18 18401: Generating pgpass > 2014-03-06 04:50:18 18401: Creating temp folder > /tmp/engine-backup.X6m3IfbCkx/tar > 2014-03-06 04:50:18 18401: Backing up files to > /tmp/engine-backup.X6m3IfbCkx/tar/files > 2014-03-06 04:50:18 18401: Backing up database to > /tmp/engine-backup.X6m3IfbCkx/tar/db/engine_backup.db > 2014-03-06 04:50:19 18401: Creating md5sum at > /tmp/engine-backup.X6m3IfbCkx/tar/md5sum > 2014-03-06 04:50:19 18401: Creating tarball ovirt.backup > 2014-03-06 04:50:19 18401: Done. > 2014-03-06 04:54:59 18685: FATAL: Engine service is active - can not restore > backup > 2014-03-06 04:55:29 18742: Restoring... > 2014-03-06 04:55:29 18742: Opening tarball ovirt.backup to > /tmp/engine-backup.uhgg5ewqOL > 2014-03-06 04:55:29 18742: Verifying md5 > 2014-03-06 04:55:29 18742: Verifying version > 2014-03-06 04:55:29 18742: Restoring files > 2014-03-06 04:55:30 18742: Reloading configuration > 2014-03-06 04:55:30 18742: Generating pgpass > 2014-03-06 04:55:30 18742: Verifying connection > ?column? > ---------- > 1 > (1 row) > > 2014-03-06 04:55:31 18742: FATAL: Database is not empty > 2014-03-06 04:58:54 20173: Restoring... > 2014-03-06 04:58:54 20173: Opening tarball ovirt.backup to > /tmp/engine-backup.VhdaFg7Gpq > 2014-03-06 04:58:54 20173: Verifying md5 > 2014-03-06 04:58:54 20173: Verifying version > 2014-03-06 04:58:54 20173: Restoring files > 2014-03-06 04:58:55 20173: Reloading configuration > 2014-03-06 04:58:55 20173: Generating pgpass > 2014-03-06 04:58:55 20173: Verifying connection > ?column? > ---------- > 1 > (1 row) > > > Seemed like restore might have worked despite the worrying FATAL message, Why does it seem so? The above seems like a concatenation of various different logs (or you used the same log file for different runs), based on timestamps. Seems like it always failed immediately after 'FATAL:'. > but when running the service nothing opens in the browser (which is a > familiar result of not having a DB properly configured). *** This bug has been marked as a duplicate of bug 1066654 *** |
Description of problem: Running engine-backup (in restore mode), following an engine-cleanup, results in the following error: "FATAL: Database is not empty" Version-Release number of selected component (if applicable): oVirt 3.4.0 RC. How reproducible: Always (well, one out of one for me). Steps to Reproduce: 1. Run "engine-setup". 2. Configure all sorts of things on engine. 3. Run "engine-backup --mode=backup --file=ovirt.backup --log=ovirt.log" 4. Run "engine-cleanup". 5. Run "engine-backup --mode=restore --file=ovirt.backup --log=ovirt.log" Actual results: Get the aforementioned error. Expected results: The deployment is restored. Additional info: Log file looks like this: 2014-03-06 04:50:18 18401: Backing up... 2014-03-06 04:50:18 18401: Generating pgpass 2014-03-06 04:50:18 18401: Creating temp folder /tmp/engine-backup.X6m3IfbCkx/tar 2014-03-06 04:50:18 18401: Backing up files to /tmp/engine-backup.X6m3IfbCkx/tar/files 2014-03-06 04:50:18 18401: Backing up database to /tmp/engine-backup.X6m3IfbCkx/tar/db/engine_backup.db 2014-03-06 04:50:19 18401: Creating md5sum at /tmp/engine-backup.X6m3IfbCkx/tar/md5sum 2014-03-06 04:50:19 18401: Creating tarball ovirt.backup 2014-03-06 04:50:19 18401: Done. 2014-03-06 04:54:59 18685: FATAL: Engine service is active - can not restore backup 2014-03-06 04:55:29 18742: Restoring... 2014-03-06 04:55:29 18742: Opening tarball ovirt.backup to /tmp/engine-backup.uhgg5ewqOL 2014-03-06 04:55:29 18742: Verifying md5 2014-03-06 04:55:29 18742: Verifying version 2014-03-06 04:55:29 18742: Restoring files 2014-03-06 04:55:30 18742: Reloading configuration 2014-03-06 04:55:30 18742: Generating pgpass 2014-03-06 04:55:30 18742: Verifying connection ?column? ---------- 1 (1 row) 2014-03-06 04:55:31 18742: FATAL: Database is not empty 2014-03-06 04:58:54 20173: Restoring... 2014-03-06 04:58:54 20173: Opening tarball ovirt.backup to /tmp/engine-backup.VhdaFg7Gpq 2014-03-06 04:58:54 20173: Verifying md5 2014-03-06 04:58:54 20173: Verifying version 2014-03-06 04:58:54 20173: Restoring files 2014-03-06 04:58:55 20173: Reloading configuration 2014-03-06 04:58:55 20173: Generating pgpass 2014-03-06 04:58:55 20173: Verifying connection ?column? ---------- 1 (1 row) Seemed like restore might have worked despite the worrying FATAL message, but when running the service nothing opens in the browser (which is a familiar result of not having a DB properly configured).