Bug 1655797 - [RFE] C&U : Remove Max VMs column in VM Planning Report page
Summary: [RFE] C&U : Remove Max VMs column in VM Planning Report page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.2
Assignee: Oleg Barenboim
QA Contact: Nandini Chandra
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-03 23:29 UTC by Nandini Chandra
Modified: 2019-01-27 00:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-27 00:27:01 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)
screen shot of Planning Report page (62.07 KB, image/png)
2018-12-03 23:29 UTC, Nandini Chandra
no flags Details

Description Nandini Chandra 2018-12-03 23:29:28 UTC
Created attachment 1511142 [details]
screen shot of Planning Report page

Description of problem:
-----------------------
The Planning report page that shows the best hosts/clusters for VMs correctly shows the following columns.
1)vCPU count, 2)Memory size, 3)disk space

It has an additional column, Max VMs. This column is not needed and should be removed.See attached screen shot.


Version-Release number of selected component (if applicable):
------------------------------------------------------------
5.9
5.10


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


Steps to Reproduce:
-------------------
1.Manage a provider.Enable C&U for the provider
2.Navigate to the Optimize -> Planning page.
3.On the left, provide some input such as : Reference VM selection, VM options, Target options etc.


Actual results:
---------------
VM Planning Report page has an extra column, Max VMs


Expected results:
-----------------
The redundant column should be removed from the VM Planning Report page.


Additional info:
----------------


Note You need to log in before you can comment on or make changes to this bug.