Description of problem: Service ovirt-engine need to be restarted after installing DWH on separate host,. : Could not fetch dashboard data ERROR [org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataServlet] (default task-30) [] Unable to retrieve d ashboard data: org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataException: Error while running SQL query IJ000453: Unable to get managed connection for java:/DWHDataSource IJ031084: Unable to create connection Version-Release number of selected component (if applicable): ovirt-engine-dwh-4.0.2-1.el7ev.noarch ovirt-engine-dashboard-1.0.1-0.el7ev.x86_64 4.0.2-3 How reproducible: 100% Steps to Reproduce: 1. engine-setup of engine (without only DWH) 2. engine-setup of dwh (only DWH) 3. open webadmin and check dashboard 4. restarting engine solve the problem Actual results: Error! Could not fetch dashboard data. Please ensure that data warehouse is properly installed and configured. Expected results: Should works on first time Additional info: Attached logs from engine and dwh
Created attachment 1187466 [details] dwh log
Created attachment 1187467 [details] engine-logs
If the intention is that the engine will monitor configuration files and reload them if changed, please open a bug on the engine. Otherwise, an engine restart is required. When setting up dwh, you were asked about how to access the engine machine, and was offered two choices - using ssh as root or manual. If user chooses root_ssh, we can restart the engine automatically, but probably want to ask the user to confirm that.
Yaniv - please ack comment 3 and change subject accordingly. Thanks.
(In reply to Yedidyah Bar David from comment #3) > If the intention is that the engine will monitor configuration files and > reload them if changed, please open a bug on the engine. Otherwise, an > engine restart is required. This is correct and a bug like this should be opened. > > When setting up dwh, you were asked about how to access the engine machine, > and was offered two choices - using ssh as root or manual. If user chooses > root_ssh, we can restart the engine automatically, but probably want to ask > the user to confirm that. I'm changing to a text bug to request the admin to restart the engine to got to the new DWH installation. We will not do this for him.
[ INFO ] Starting dwh service Please restart the engine by running the following on 10-34-60-45.rhev.lab.eng.brq.redhat.com : # service ovirt-engine restart This is required for the dashboard to work. --== END OF SUMMARY ==-- [ INFO ] Stage: Clean up verified in ovirt-engine-dwh-setup-4.0.6-1.el7ev.noarch