Bug 1369001
Summary: | Cockpit "Virtualization" dashboard should handle stopped VDSM gracefully | ||
---|---|---|---|
Product: | [oVirt] ovirt-node | Reporter: | Ondřej Svoboda <osvoboda> |
Component: | UI | Assignee: | Marek Libra <mlibra> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Wei Wang <weiwang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.0 | CC: | bugs, dfediuck, gklein, mgoldboi, michal.skrivanek, rbarry, tjelinek, trichard, weiwang |
Target Milestone: | ovirt-4.0.4 | Flags: | ykaul:
ovirt-4.0.z+
mgoldboi: planning_ack+ tjelinek: devel_ack+ ykaul: testing_ack+ |
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
On the Virtualization page in Cockpit, if VDSM is not running on the host, the user is informed and steps to resolve the issue are provided. This might happen, in particular, when the self-hosted engine is not yet deployed or the host is not yet added to a cluster.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-29 11:16:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ondřej Svoboda
2016-08-22 10:10:59 UTC
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 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. (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 |