This repository has been archived by the owner on Jul 1, 2021. It is now read-only.
Allow deployOvf to function even when DNS is not fully configured. #141
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.
We observed an issue when hosts were added to vCenter via a FQDN, but
DNS was not functioning end to end in the environment, specifically at
the location where the deployOvf call was initiated. Thus deploying an
Ovf failed. This updates the upload command to always ensure a valid
location by IP even when DNS is not available at the calling location.