Created attachment 1029787 [details] restore log for 3.4 environment Description of problem: Following on from email: Restoring reports as part of engine-backup does not seem to restore the reports as freshly install them to the backed up engine. Version-Release number of selected component (if applicable): 3.4 & 3.5 - this particular instance was 3.4 How reproducible: For me it has been 100% Steps to Reproduce: 1. Create custom dashboard in reports 2. Use engine-backup to backup engine, reports, and dwh dbs (and files) 3. Restore all (procedure being used is http://docbuilder.usersys.redhat.com/22765/#Restoring_a_Backup_to_a_Fresh_Installation) Actual results: The restore seems to work - engine backup is completed, reports running - but the custom dashboard does not exist. Expected results: The reports portal is restored with any custom resources. Additional info: This bug is being raised as part of documentation testing for writing the aforementioned procedure. If the fault is with the documentation, my apologies; corrections are appreciated. The custom dashboard is being backed up - I can find it in the db bkup.
Created attachment 1029788 [details] 3.4 engine log
Created attachment 1029789 [details] the most recent setup log
Now verified that this happens on 3.4.5 "upgrading" to itself. Changed summary accordingly, and a few other fields.
Hi, in ovirt reports there aren't any adhoc reports, so it cannot be verified in ovirt (ovirt-3.6.0-3)
In principle you can use upstream code with jasperreports-server-pro. This is a supported flow, in principle. In practice it might be better to wait for a first downstream build which is expected soon. As you can see in the patch page in gerrit, I verified it on 3.5 only.
Didi already answered in comment #9, dropping needinfo on me
How is BZ #1255434 related? this is a upgrade flow the other a restore flow.
(In reply to Yaniv Dary from comment #11) > How is BZ #1255434 related? this is a upgrade flow the other a restore flow. In BZ #1255434 I don't make an upgrade. If I know correctly, I cannot restore database via engine-backup without clean engine. In reproduction steps (2 and 3) in comment #0 I must backup all and restore all. So my steps for verifying this is: Create a custom dashboard in reports backup all engine-cleanup (for restoring the backup) restore all make engine-setup (issue described in BZ #1255434) Check the dashboard in reports
Ahh, now I understand what you mean. It confuses me the backup and restore part in comment #0. So if I understand it correctly, just create dashboard in 3.5, upgrade to 3.6 and check the dashboard ? (the issue was in upgrade process ?)
(In reply to Petr Kubica from comment #13) > Ahh, now I understand what you mean. It confuses me the backup and restore > part in comment #0. So if I understand it correctly, just create dashboard > in 3.5, upgrade to 3.6 and check the dashboard ? (the issue was in upgrade > process ?) You create a ad hoc report and save it to saved reports folder (any other location is not saved) then upgrade and make sure that it kept and not deleted.
Verified in rhevm-reports-3.6.0-0.6.el6ev.noarch
Added some commas, hope that's ok
Looks good. Thanks for the added commas. :)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0425.html