Description of problem: In https://bugzilla.redhat.com/show_bug.cgi?id=1212306 there was a fix https://bugzilla.redhat.com/show_bug.cgi?id=1212306#c1 . If there is no table "jidashboardmodel" we create it. engine-setup with the fixed version is still failing for non-existent table Version-Release number of selected component: Mar 07 14:52:49 Installed: jasperreports-server-pro-5.5.0-10.el6ev.noarch Mar 07 14:53:03 Installed: rhevm-reports-setup-3.5.8-1.el6ev.noarch Mar 07 14:53:04 Installed: rhevm-reports-3.5.8-1.el6ev.noarch --> Mar 29 15:57:50 Updated: jasperreports-server-pro-6.0.1-5.el6ev.noarch Mar 29 15:57:51 Updated: rhevm-reports-3.6.3-1.el6ev.noarch Mar 29 15:57:52 Updated: rhevm-reports-setup-3.6.3-1.el6ev.noarch for some reason, even if the engine-setup failed, we upgraded rhevm-reports. How reproducible: Everytime Steps to Reproduce: 1. Install 3.5.8 reports/dwh on separate server 2. yum update 3. engine-setup Actual results: failing here: ... Resource name: applicationContext-themes-pro.xml Resource name: applicationContext-virtual-data-source.xml ERROR: relation "jidashboardmodel" does not exist Position: 4358 com.jaspersoft.jasperserver.api.JSExceptionWrapper: could not execute query; SQL (I will upload the sosreport in case the rest is needed) Expected results: Create the non-existent table and finish successfully Additional info: RHEV-M and DWH/Reports are on different servers
Closing as duplicate of bug 1290040. If you think it's a different flow, please give more details, including exact flow and yum.log. Thanks. *** This bug has been marked as a duplicate of bug 1290040 ***