Hyper-V PowerShell Module is not available error when module is installed

[dariusj18]

Environment:

Minikube version (use minikube version): v0.25.1

• OS (e.g. from /etc/os-release): Windows 10 Pro
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): n/a
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): n/a
• Install tools: Installed via isntaller and choco (same result)

What happened:

PS C:\WINDOWS\system32> minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch"
Starting local Kubernetes v1.9.4 cluster...
Starting VM...
E0322 15:54:09.998217 13800 start.go:159] Error starting host: Error creating host: Error executing step: Running precreate checks.
: Hyper-V PowerShell Module is not available.

Retrying.
E0322 15:54:10.002181 13800 start.go:165] Error starting host: Error creating host: Error executing step: Running precreate checks.
: Hyper-V PowerShell Module is not available
PS C:\WINDOWS\system32>

How to reproduce it (as minimally and precisely as possible):
Run minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch"

Anything else do we need to know:

It looks like line

minikube/vendor/github.com/docker/machine/drivers/hyperv/powershell.go

Line 64 in a000c35

if resp[0] != "Hyper-V" {

expects "Hyper-V", however when I run @(Get-Command hyper-v\Get-VM).ModuleName i get hyper-v (lowercase)

[dariusj18]

It looks like the version 1.1 of the Module reports as Hyper-V whereas the 2.0.0.0 reports as hyper-v

[jordansissel]

I am getting this error also.

> minikube --hyperv-virtual-switch=External --vm-driver hyperv start
Starting local Kubernetes v1.9.4 cluster...
Starting VM...
E0322 15:35:50.113731   14884 start.go:159] Error starting host: Error creating host: Error executing step: Running precreate checks.
: Hyper-V PowerShell Module is not available.

 Retrying.
E0322 15:35:50.118733   14884 start.go:165] Error starting host:  Error creating host: Error executing step: Running precreate checks.
: Hyper-V PowerShell Module is not available

For an odd data point, the module name is "Hyper-V" for me when I check directly, but minikube sees it the same as @dariusj18?

> minikube.exe version
minikube version: v0.25.1

> @(get-command get-vm).ModuleName
Hyper-V

> @(get-command hyper-v\get-vm).ModuleName
Hyper-V

Running minikube verbose:

> minikube --hyperv-virtual-switch=External --vm-driver hyperv --v 7 start
Starting local Kubernetes v1.9.4 cluster...
Starting VM...
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive @(Get-Command hyper-v\Get-VM).ModuleName
[stdout =====>] : hyper-v
...

Powershell -NoProfile, it's hyper-v lowercase?

> powershell -noprofile
> get-command hyper-v\get-vm

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Cmdlet          Get-VM                                             2.0.0.0    hyper-v

Powershell interactive/default, it's Hyper-V ?

PS C:\Users\jls> get-command hyper-v\get-vm

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Cmdlet          Get-VM                                             2.0.0.0    Hyper-V

I confess to not know what exactly is causing this. It's very strange, and I'm not convinced minikube is the problem, but maybe just a case-insensitive check will fix this?

[saitho]

#2639

[govind22]

I'm also getting this error.

I'm running win 10 with latest updates

[gbraad]

This should have been fixed with syncing: https://github.com/docker/machine/blob/1e3b6b64504f2970252b06119d6dc1fb1982b4b4/drivers/hyperv/hyperv.go

[gbraad]

For docker-machine, you need to have https://github.com/docker/machine/tree/1e3b6b64504f2970252b06119d6dc1fb1982b4b4/drivers/hyperv compiled as binary... however at the moment they haven't tagged and/or released this: Related issues: docker-archive-public/docker.machine#4424, docker-archive-public/docker.machine#4441

…

On Tue, Apr 3, 2018 at 2:20 AM, Gerard Braad ***@***.***> wrote: This should have been fixed with syncing: https://github.com/kubernetes/minikube/tree/125eede1530caca69ce442f58b9ce703434f5388/vendor/github.com/docker/machine/drivers/hyperv Make sure you run v0.25.2 => https://github.com/kubernetes/minikube/releases/tag/v0.25.2

-- Gerard Braad | http://gbraad.nl [ Doing Open Source Matters ]

[F21]

I am seeing this after upgrading to Minikube 0.26.0 on Windows 10 64-bit.

[andrewsav-bt]

@dariusj18 Not really, there is something else going on:

[gbraad]

They merged #2586, but this is a problematic PR... They should take #2634 (comment) as it uses the correct casing (this does affect, as we saw the same in Minishift) @dlorenc Please take: https://github.com/docker/machine/blob/1e3b6b64504f2970252b06119d6dc1fb1982b4b4/drivers/hyperv/hyperv.go ! /cc: @r2d4 @aaron-prindle

[AndrewSav]

@gbraad it does not appear that there is a "correct casing", rather that should be case insensitive. Also what is interesting, I don't have this problem with 0.25.2 only with 0.26.0.

[gbraad]

Well, we have experienced the same problem on Minishift's end. This fix was only taken for the latest point-release, so you are right to say you didn't have this with 0.25.2. If you actually look carefully at https://github.com/kubernetes/minikube/commits/v0.25.2 you can see @r2d4 took the fix I suggested => d564056 with the correct case. However, for some reason this fix is not in the master branch (and therefore also not in the 0.26.0 tagged release). The PR I pushed also changes the test to:

PS> @(Get-Module -ListAvailable hyper-v).Name | Get-Unique

which returns:

Hyper-V

Related issues: docker-archive-public/docker.machine#4426, docker-archive-public/docker.machine#4424, docker-archive-public/docker.machine#4441, and a ton of others on the Docker/machine end.

Minikube original synced docker/machine version 0.14.0 as tag, but these fixes only came AFTER the release was made. they are included in the Docker edge releases, but as of now, it is still untagged.

[AndrewSav]

@gbraad I'd like to repeat myself that there is no "correct case" this powershell module names are case insensitive. I have two machines with the same version of Windows, and Powershell and the case returned for the module is different (see here) unless you know explanation for that, the comparison should be case insensitive, as some other links I saw (sorry do not have them now) suggest that the module names in powershell are case insensitive.

I don't care as long as it works, I'm just pointing out, that stating that there is a "correct" case is dangerous, since empirical testing shows it's wrong.

[surajsubs]

With 0.26.0, I was having the same issue reported here. I noticed that the case of module name changes, between powershell and powershell in administrative mode. See screenshots below

Powershell Administrative mode

Regular Powershell

Downgrading to 0.25.2 did resolve the issue.