Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 990516

Summary: Unmanaged VMs are reported in main host tab, but invisible in VMs subtab
Product: [Retired] oVirt Reporter: Assaf Muller <amuller>
Component: ovirt-engine-webadminAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3CC: acathrow, ecohen, iheim, mgoldboi, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 07:21:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Assaf Muller 2013-07-31 11:14:44 UTC 
Description of problem:
vdsClient -s 0 list table returns 2 VMs.
One was created via the engine, and the other via virsh (Not through the engine).

Version-Release number of selected component (if applicable):
oVirt Engine Version: 3.3.0_master
vdsm-4.12.0-rc3.15.gite62edfc.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install a new host
2. Create a VM through virsh
3. Create a 2nd VM through the engine

Actual results:
Hosts main tab reports 2 VMs on the host
VMs subtab reports only 1 VM (The one created through the engine)

Expected results:
The easy way out: Only report the VMs created through the engine
The better way - Show all VMS in the subtab. Ones not created through engine will be greyed out
The best way - Show all VMs in the subtab and allow management of all VMs, including ones not created through the engine
Comment 1 Assaf Muller 2013-07-31 11:17:05 UTC 
Correction: It looks like the original VM was created via vdsClient or through another engine.
Comment 2 Itamar Heim 2013-08-01 07:21:14 UTC 
i'm closing this as not a bug, since it is not currently a supported flow and is the expected behavior.
we are actually planning to fix this behavior for hosted engine soon.