Bug 1390408 - Vmware Storage Profile in vsphere55
Summary: Vmware Storage Profile in vsphere55
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.7.0
Assignee: Adam Grare
QA Contact: Leo Khomenko
URL:
Whiteboard: vmware:ui
Depends On: 1386706
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-01 01:09 UTC by Satoe Imaishi
Modified: 2017-01-04 13:06 UTC (History)
8 users (show)

Fixed In Version: 5.7.0.7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1386706
Environment:
Last Closed: 2017-01-04 13:06:58 UTC
Category: ---
Cloudforms Team: VMware
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
copy of Request which created Vm with Storage Profile (41.33 KB, image/png)
2016-11-01 14:35 UTC, Leo Khomenko 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0012 0 normal SHIPPED_LIVE CFME 5.7.0 bug fixes and enhancement update 2017-01-04 17:50:36 UTC

Comment 2 Leo Khomenko 2016-11-01 14:35:17 UTC 
Created attachment 1216136 [details]
copy of Request which created Vm with Storage Profile

if you copy Request with Storage profile - information about selected Storage Profile is not shown and Profile is not pre-selected in new Request. this happens in VC55 and VC6
Comment 3 Leo Khomenko 2016-11-01 14:37:53 UTC 
Adam, please decide if above should be a new RFE BZ or this can be done as part of this one
P.S. in general Storage Profiles are shown during provisioning and in Vm details
Comment 4 Adam Grare 2016-11-01 14:42:07 UTC 
Leo that looks like a different bug, probably in the provisioning dialogs.
Can you open a new BZ for that?
Comment 5 Leo Khomenko 2016-11-02 17:17:27 UTC 
ok. opening separate BZ for that issue in dialogs
Comment 7 errata-xmlrpc 2017-01-04 13:06:58 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://rhn.redhat.com/errata/RHBA-2017-0012.html
Note You need to log in before you can comment on or make changes to this bug.