Skip to content
This repository was archived by the owner on Jul 28, 2020. It is now read-only.
This repository was archived by the owner on Jul 28, 2020. It is now read-only.

CFDEV fail to start on Windows with conflicting Powershell modules installed #111

@shouah

Description

@shouah

Summary:
When running CFDEV on Windows 10 which has powershell modules for both Hyper-V and VMware PowerCLI installed, which has duplicated commands like Get-VM, then then CF CLI plugin invokes the wrong command and fails unexpectedly.

Expected behavior:
The command "cf dev start -f ...tgz" invokes the correct PowerShell commands under the hood

Observed behavior:

> cf dev start -f .\pcfdev-v1.2.0-windows.tgz
FAILED
cf dev start: is running: getting vms: failed to execute: powershell.exe -Command "Get-VM -Name cfdev*": exit status 1: Get-VM : 8/20/2019 10:33:14 AMGet-VM          You are not currently connected to any servers. Please connect first using a Connect cmdlet.
At line:1 char:1
+ Get-VM -Name cfdev*
+ ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [Get-VM], ViServerConnectionException
    + FullyQualifiedErrorId : Core_BaseCmdlet_NotConnectedError,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetVM

Request:
Either:

  1. Update the plugin to explicitly prefix all PowerShell commands with the Hyper-V prefix to ensure ambiguous execution, for example:

powershell.exe -Command "Hyper-V\Get-VM -Name cfdev*"

  1. Or provide a start command line option to specify the PowerShell prefix to be used, something like:

cf dev start -f ...tgz -psprefix "Hyper-V"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions