Bug 1300851 - [RFE] Add customize tab to VM provision for SCVMM to enable Sysprep selection
Summary: [RFE] Add customize tab to VM provision for SCVMM to enable Sysprep selection
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: John Hardy
QA Contact: Jeff Teehan
URL:
Whiteboard: automate:custom:provision
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-21 22:39 UTC by Jeff Teehan
Modified: 2017-08-28 15:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-28 15:01:26 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jeff Teehan 2016-01-21 22:39:04 UTC
Description of problem:

The customize tab does not appear for SCVMM hosted templates.  This means you can't attach a sysprep customization to a Template.  The results is that any SCVMM Template which has been sysprepped will fail from the SCVMM side.

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

How reproducible:
Always

Steps to Reproduce:
1.  Provision VM
2.  Select a template from an SCVMM Provider
3.  Look for Customize tab.

Actual results:
The tab does not appear.  It does appear from VMWare Templates.

Expected results:


Additional info:
There is a workaround in that the unattended.xml can be directly attached to a template from within SCVMM, but you won't be able to select one on the fly from CFME.

Comment 3 Chris Pelland 2017-08-28 15:01:26 UTC
This bug has been open for more than a year and is assigned to an older release of CloudForms. 
If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.


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