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

Bug 921380

Summary: [RHEVM-RHS] Do not display fields related to VMs in 'General' sub-tab for a host in a gluster-cluster
Product: Red Hat Enterprise Virtualization Manager Reporter: Shruti Sampat <ssampat>
Component: ovirt-engine-webadmin-portalAssignee: Kanagaraj <kmayilsa>
Status: CLOSED WONTFIX QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.0CC: dpati, dtsang, ecohen, grajaiya, iheim, jkt, knarra, mmahoney, pprakash, rbalakri, Rhev-m-bugs, sabose, sankarshan, scohen, sdharane, shtripat
Target Milestone: ---Flags: dpati: Triaged+
Target Release: 3.5.0   
Hardware: All   
OS: All   
Whiteboard: gluster
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-23 07:11:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Shruti Sampat 2013-03-14 05:28:39 UTC 
Created attachment 709874 [details]
screenshot

Description of problem:
---------------------------------------
For a host in a gluster-cluster, the General sub-tab shows the following fields - 

Active VMs
Max free Memory for scheduling new VMs

These fields neet not be shown for a node in a gluster-cluster.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.2.0-10.14.beta1.el6ev 

How reproducible:
Always

Steps to Reproduce:
1. Under the Hosts tab, select a host that is part of a gluster-cluster.
  
Actual results:
The above mentioned fields are seen.

Expected results:
These fields are related to VMs and hence should not be shown for a storage node in a gluster-cluster.

Additional info:
Comment 3 Sahina Bose 2014-09-23 07:11:45 UTC 
Closing this as WONTFIX as this is a low impact bug
Please re-open if this needs to be fixed.