Bug 1565763

Summary: [VMWare]Sysprep customization doesn't start
Product: Red Hat CloudForms Management Engine Reporter: Leo Khomenko <lkhomenk>
Component: ProvisioningAssignee: Patrik Kománek <pkomanek>
Status: CLOSED ERRATA QA Contact: Kedar Kulkarni <kkulkarn>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: agrare, akarol, cpelland, gblomqui, gmccullo, jfrey, jhardy, obarenbo, simaishi
Target Milestone: GA   
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sysprep:vmware
Fixed In Version: 5.10.0.11 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 23:01:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: VMware Target Upstream Version:
Attachments:
Description Flags
provision log example none

Comment 2 Leo Khomenko 2018-04-10 17:51:57 UTC
Created attachment 1420002 [details]
provision log example

Comment 3 Adam Grare 2018-04-10 20:36:07 UTC
Leo, did this used to work with the same sysprep file on a previous CFME version?

Comment 7 Greg McCullough 2018-04-25 12:59:22 UTC
This flag only applies to VMware since we support the Customization Specs and allow users to override the values in the spec or use exactly as defined.

Lucy - Please review and let me know if you need to discuss.

Comment 8 Greg McCullough 2018-04-25 13:24:11 UTC
Re-assigned to Patrik

Comment 10 Patrik Kománek 2018-08-06 09:38:46 UTC
Solved in https://github.com/ManageIQ/manageiq-providers-vmware/pull/308

Comment 11 Kedar Kulkarni 2018-11-08 21:24:03 UTC
On 5.10.0.23 Sysprep templates are working for VMware with win2012 as explained in Comment 1

Comment 13 errata-xmlrpc 2019-02-07 23:01:41 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-2019:0212