Bug 1761966 - Available disk space not shown under Optimize Utilization for VMWare provider
Summary: Available disk space not shown under Optimize Utilization for VMWare provider
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.10.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.12.0
Assignee: Libor Pichler
QA Contact: Nandini Chandra
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1773577 1773579
TreeView+ depends on / blocked
 
Reported: 2019-10-15 18:11 UTC by Tuan
Modified: 2023-03-24 15:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1773577 1773579 (view as bug list)
Environment:
Last Closed: 2020-06-10 12:53:19 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
datastores (20.27 KB, image/png)
2019-10-15 18:12 UTC, Tuan 		no flags Details
utilization (64.38 KB, image/png)
2019-10-15 18:14 UTC, Tuan 		no flags Details
table view (13.07 KB, image/png)
2019-10-15 18:15 UTC, Tuan 		no flags Details
View All

Description Tuan 2019-10-15 18:11:39 UTC 
Description of problem:

Under Optimize -> Utilization available disk space is not shown for vCenter providers in our environments.  Is this expected behavior?  See attached screenshot.

Consultant is on site

We show the total and max used but no available value. This should be able to be calculated. 


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

How reproducible:
Everytime

Steps to Reproduce:
1.Optimize--> Utilization
2.Available disk space does not show
3.

Actual results:


Expected results:


Additional info:
Comment 2 Tuan 2019-10-15 18:12:14 UTC 
Created attachment 1626104 [details]
datastores
Comment 3 Tuan 2019-10-15 18:14:10 UTC 
Created attachment 1626105 [details]
utilization
Comment 4 Tuan 2019-10-15 18:15:59 UTC 
Created attachment 1626112 [details]
table view
Note You need to log in before you can comment on or make changes to this bug.