Bug 1393776 - Vmware Storage Profile is not shown in Provisioning Request
Summary: Vmware Storage Profile is not shown in Provisioning Request
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: GA
: 5.8.0
Assignee: James Wong
QA Contact: Leo Khomenko
URL:
Whiteboard: storage:ui:vsphere
Depends On:
Blocks: 1396580
TreeView+ depends on / blocked
 
Reported: 2016-11-10 10:26 UTC by Leo Khomenko
Modified: 2017-06-12 16:19 UTC (History)
8 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1396580 (view as bug list)
Environment:
Last Closed: 2017-06-12 16:19:39 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


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

Description Leo Khomenko 2016-11-10 10:26:06 UTC
Created attachment 1219303 [details]
copy of Request which created Vm with Storage Profile

Description of problem:when you create a request to provision a VM with pre-selected storage profile it's not shown in Request on Environment tab, which affect Copy of this request - Storage profile is not defined if we copy a Request which had a Storage profile


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


How reproducible:always


Steps to Reproduce:
1.provision a VM on VC provider with Storage profile
2.Open Request / Environment

Actual results: Storage Profile is empty


Expected results:Storage Profile should be shown if it was selected during Provision


Additional info:Provisioning a VM with the Storage Profile is working. Cloning a VM with Storage Profile is also fine - profile is predefined and shown.
In 1390408 it was mentioned that this is not a Provider issue.

Comment 5 James Wong 2016-11-14 22:15:14 UTC
The allowed_storage_profile method that would populate the field of storage profile for the request is always select the selected VM template's storage profile. So when a template being used doesn't have storage profile, the request's storage profile field will show empty.

Comment 6 James Wong 2016-11-17 20:17:23 UTC
PR for the fix is merged https://github.com/ManageIQ/manageiq/pull/12627

Comment 8 Leo Khomenko 2017-02-09 14:49:43 UTC
was verified in 5.6.4 and 5.7.1.1


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