This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
Fix issue #4342 - PowerShell cmdlet name collision with VMware PowerCLI #4404
+18
−18
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
|
Please sign your commits following these rules: $ git clone -b "4342-powercli-collision" [email protected]:davemay99/machine.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -fAmending updates the existing PR. You DO NOT need to open a new one. |
Signed-off-by: Dave May <[email protected]>
davemay99
force-pushed
the
4342-powercli-collision
branch
from
f4d0d2a
to
15095c9
Compare
|
LGTM |
|
I've installed version 0.14.0-rc1, build e918c74, but I'm getting the error reported: "Error with pre-create check: "Hyper-V PowerShell Module is not available". Does anyone have advice one what I should be looking out for? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When VMware PowerCLI is installed alongside Hyper-V, there are multiple command collisions which prevent the hyperv machine driver from working as expected. This issue is reported in #4342, and is fixed by prepending the hyper-v module name to ensure the correct module is used.