Customization fix #308
Merged
Customization fix #308
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pkomanek
force-pushed
the
broken_customization_during_vm_provisioning_fix
branch
3 times, most recently
from
acf9edd
to
4e390e0
Compare
pkomanek
force-pushed
the
broken_customization_during_vm_provisioning_fix
branch
from
4e390e0
to
00adb1e
Compare
|
Checked commits pkomanek/manageiq-providers-vmware@6468dff~...00adb1e with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
agrare
approved these changes
Aug 3, 2018
agrare
added a commit
that referenced
this pull request
Aug 3, 2018
…provisioning_fix Customization fix
agrare
pushed a commit
to agrare/manageiq-providers-vmware
that referenced
this pull request
Apr 15, 2019
…ured_system Email instances for /Infrastructure/Configured_System provisioning.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for broken customization(sysprep) during vm provisioning.
Description: Customizing Windows template with sysprep during provision didn't apply any changes to VM.
Steps to Reproduce:
1.Initiate VM provision with sysprep customization
2.on Customize tab/Sysprep Answer File upload unattended answer xml file(or select one of Customization Templates created on the Vmware provider side)
https://bugzilla.redhat.com/show_bug.cgi?id=1565763