Ignore esxi_hostname at VM creation when vcenter_hostname is not defined #486
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
Signed-off-by: Qi Zhang <qiz@vmware.com>
|
LGTM. @keirazhang |
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.
If there is no vcenter_hostname defined in vars/test.yml, vsphere_host_name will be same with esxi_hostname, and
common/vm_create.ymlwill report error like "Unable to find host". It means that esxi_hostname is required when vsphere_host_name = vcenter_hostname for this task. The solution is to ignore esxi_hostname when vsphere_host_name = esxi_hostname.