Red Hat Bugzilla – Bug 1067551
engine-backup script is not taking the backup of rhevm-report.
Last modified: 2015-03-22 20:46:36 EDT
Description of problem: Currently the 'engine-backup' script is not taking the backup of rhevm-report install on the rhevm system. Version-Release number of selected component (if applicable): rhevm 3.3 How reproducible: 100% Steps to Reproduce: 1. install a rhevm system and configure the rhevm-reports 2. take the backup using engine-backup script. 3. install a new rhevm system and install the rhevm-reports package. Then use the engine-backup script to restore the backup taken from the old system. It will fail. Actual results: Restore is failing as rhevm-report configuration files are not backed up. Expected results: It should take the backup of the rhevm-report configuration files also.
(In reply to Udayendu Sekhar Kar from comment #0) > Description of problem: > Currently the 'engine-backup' script is not taking the backup of > rhevm-report install on the rhevm system. > > Version-Release number of selected component (if applicable): > rhevm 3.3 > > How reproducible: > 100% > > Steps to Reproduce: > 1. install a rhevm system and configure the rhevm-reports > 2. take the backup using engine-backup script. > 3. install a new rhevm system and install the rhevm-reports package. I assume you have executed the rhevm-reports-setup post the second installation ? > Then > use the engine-backup script to restore the backup taken from the old > system. It will fail. What fails ? the restore of the engine db ? If it fails than we need the restore logs. > > > Actual results: > Restore is failing as rhevm-report configuration files are not backed up. > > Expected results: > It should take the backup of the rhevm-report configuration files also.
Notes to QE. See --help for changes. You now must run setup after restore. Reports will definitely not work without setup, engine might work, didn't test dwh. Some relevant flows to verify: setup/backup/cleanup/restore/setup on same machine, no credentials change, engine only same, engine+dwh same, engine+dwh+reports same but after cleanup change the installed applications - e.g. after engine-only backup/cleanup, install also dwh+reports and restore/setup. Also opposite - after engine+dwh+reports backup, remove dwh and/or reports and restore/setup some/all of the above with changed credentials - for engine, dwh, reports, one or more creds changes at once some/all of the above but on a different/new/clean machine/db Note that probably not all of the scenarios will finish exactly as expected. Not sure all such cases are bugs. I think the minimum requirement is only that setup after restore finishes successfully and whatever was setup by it works. I personally verified only very few flows. I also updated the wiki page http://www.ovirt.org/Ovirt-engine-backup . Comments/ideas/opinions/reports/results are welcome :-)
Verified on av8.1 1) --help, new options 2) Backup / restore sequences: i) Backup / restore a) setup/backup/cleanup/restore/setup on same machine, no credentials change, engine only b) setup/backup/cleanup/restore/setup on same machine, no credentials change, engine + dwh c) setup/backup/cleanup/restore/setup on same machine, no credentials change, engine + dwh + reports ii) Adding components during Backup / restore process a) setup engine /backup/cleanup install dwh /restore/setup on same machine b) setup engine /backup/cleanup install dwh + reports /restore/setup on same machine c) setup engine + dwh /backup/cleanup install reports /restore/setup on same machine iii) Removing components during Backup / restore process a) setup engine + dwh + reports /backup/cleanup remove reports /restore/setup n same machine b) setup engine + dwh + reports /backup/cleanup remove dwh + reports /restore/setup on same machine c) setup engine + dwh /backup/cleanup remove dwh /restore/setup on same machine iv) Backup / restore process over network (remote db configuration) a) setup/backup/cleanup/restore/setup on same machine, no credentials change, engine + dwh + reports, remote db
Thanks. updated.
Closing as part of 3.4.0