Bug 1505951 - Azure extra disk information of VM is not showing from CFME which prevents Chargeback calculation for the usage.
Summary: Azure extra disk information of VM is not showing from CFME which prevents Ch...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.8.3
Assignee: Bronagh Sorota
QA Contact: Nandini Chandra
URL:
Whiteboard: chargeback:azure
Depends On: 1503866
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-24 16:05 UTC by Satoe Imaishi
Modified: 2022-07-09 09:09 UTC (History)
10 users (show)

Fixed In Version: 5.8.3.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1503866
Environment:
Last Closed: 2018-02-28 13:07:14 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screen shot of Azure instance summary with correct disk size and type (30.68 KB, image/png)
2018-01-19 22:04 UTC, Nandini Chandra 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0374 0 normal SHIPPED_LIVE Important: Red Hat CloudForms security, bug fix, and enhancement update 2018-02-28 18:04:37 UTC

Comment 2 Satoe Imaishi 2017-10-26 17:04:59 UTC 
PR: https://github.com/ManageIQ/manageiq-providers-azure/pull/147
Comment 25 Nandini Chandra 2018-01-19 20:30:42 UTC 
Verified in 5.8.3.1
Comment 26 Nandini Chandra 2018-01-19 22:03:06 UTC 
Discussed this Bronagh. After the fix, the following should be displayed on the UI:

1)correct disk size
2)disk type

Verified that the correct disk size and disk type are displayed on the UI.
See attached screen shot.
Comment 27 Nandini Chandra 2018-01-19 22:04:40 UTC 
Created attachment 1383615 [details]
screen shot of Azure instance summary with correct disk size and type
Comment 30 errata-xmlrpc 2018-02-28 13:07:14 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0374
Note You need to log in before you can comment on or make changes to this bug.