Bug 1368453

Summary: When the gluster cluster is chosen , the policies should not be listed
Product: [oVirt] ovirt-engine Reporter: SATHEESARAN <sasundar>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED DEFERRED QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: low    
Version: 4.0.2.7CC: bugs, sabose
Target Milestone: ---Flags: sasundar: planning_ack?
sasundar: devel_ack?
sasundar: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-01 07:06:18 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:
Attachments:
Description Flags
screenshot showing the new cluster dialog window none

Description SATHEESARAN 2016-08-19 13:01:04 UTC 
Description of problem:
-----------------------
While creating a new cluster, selecting the gluster only cluster, should not list the policies that correspond to virt cluster like Scheduling Policy, Migration Policy, Fencing Policy

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHV 4.0.2-7

How reproducible:
------------------
Always

Steps to Reproduce:
-------------------
1. Create a new cluster
2. Select the cluster capability as 'Gluster'

Actual results:
---------------
The various policies are listed after selecting the cluster type as 'Gluster'

Expected results:
-----------------
The policies shown while creating a new cluster like scheduling policy, Migration Policy, Fencing policy is not relevant to cluster type 'Gluster'


Additional info:
Comment 1 SATHEESARAN 2016-08-19 13:02:03 UTC 
Created attachment 1192125 [details]
screenshot showing the new cluster dialog window
Comment 2 Sahina Bose 2016-09-01 07:06:18 UTC 
Currently hiding virt related fields is handled in "gluster" only mode, not both mode. Deferring this as this is a low priority