Description of problem: On a freshly installed NGN, user experience with ovirt-dashboard is not very friendly. Before the host is deployed, the Virtualization dashboard in Cockpit should not just display an error message that VDSM is in fact not running. Instead, it should warn the user that the host is not set up yet, and refer to a relevant guide/documentation on how to continue with deployment (either adding the host to a cluster or running hosted-engine --deploy). It is possible that the host has already been set up and VDSM is stopped for a different reason. In that case, the user should be told how to troubleshoot, e.g. by referring the user to the journal tab or to the console to see /var/logs/vdsm/(super)vdsm.log -- and then perhaps to sosreport and Bugzilla. Version-Release number of selected component (if applicable): NGN based on oVirt 4.0.2 (the relevant ovirt-dashboard Cockpit component) How reproducible: always Steps to Reproduce: 1. Install NGN, but do not start VDSM yet (or equally, do not deploy hosted engine yet). 2. Go to Cockpit. 3. Switch to Virtualization dashboard and select the "Virtual Machines" tab. Actual results: An error message appears: "Vdsm execution failed! Please check that: VDSM is set up properly (i.e. /etc/pki/vdsm/certs/cacert.pem is required) [path_to_cokcpit-ovirt-plugin]/vdsm/vdsm is executable, VDSM path: /usr/share/cockpit/ovirt-dashboard/vdsm/vdsm/vdsm" Expected results: A warning appears saying that the host/node is not set up for virtualization yet. (plus some guidance) Additional info: The VDSM executable here is a JSONRPC client which logged "connection refused" messages to the journal.
Since vdsmd.service is simply not started after the installation of NGN, perhaps the dashboard should first check its status before trying to list VMs. Or even, if this is not already done, VDSM status should be displayed on the intro page of the dashboard.
*** Bug 1365380 has been marked as a duplicate of this bug. ***
@Ryan fixed, proposing to release it in 4.0.4
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
This part of the dashboard is covered by Marek. Marek, can this be pulled into 4.0.4?
to clarify - RHEL cockpit is tech preview and not generally tracked in bugzilla, stuff is done upstream - NGN cockpit is a ovirt-node component so keeping it on ovirt-node and pending Marek to create an upstream release
(In reply to Red Hat Bugzilla Rules Engine from comment #8) > Bug tickets must have version flags set prior to targeting them to a > release. Please ask maintainer to set the correct version flags and only > then set the target milestone. alright, this is the last time I'm setting it.
Test Version redhat-virtualization-host-4.0-20160919.0.x86_64 cockpit-ws-0.114-2.el7.x86_64 cockpit-ovirt-dashboard-0.10.6-1.4.0.el7ev.noarch Test Steps: 1. Install NGN, but do not start VDSM yet (or equally, do not deploy hosted engine yet). 2. Login Cockpit with root account 3. Switch to Virtualization dashboard and select the "Virtual Machines" tab. Result: A warning appears saying that the host/node is not set up for virtualization yet. The VDSM service is not responding on this host The host is not yet properly set. Please either add the host to a cluster or deploy the Hosted Engine. If the host is already added to a cluster but VDSM is still not running, please check it's status in VDSM Service Management So the bug cannot be reproduced, change the status to VERIFIED