Skip to content

PowerCLI 6.0 modules, do they work? #1965

@TryTryAgain

Description

@TryTryAgain

Bug report:
The reason I ask, it was in the announcement demos, but it's not found in the source code demos, and doesn't appear to be working. But I hope it is, and I'm just missing something.

Steps to reproduce

Try and manually load any PowerCLI module with Import-Module and it fails...

Expected behavior

The module would be loaded and I can go on my way connecting with Connect-VIServer etc.

Actual behavior

Import-Module : The required module 'VMware.VimAutomation.Sdk' is not loaded. Load the module or remove the module from 'RequiredModules' in the file '/root/.local/share/powershell/Modules/VMware.VimAutomation.Common/VMware.VimAutomation.Common.psd1'.
At line:1 char:1

  • Import-Module VMware.VimAutomation.Cis.Core
  • - CategoryInfo          : ResourceUnavailable: (/root/.local/sh...ion.Common.psd1:String) [Import-Module], MissingMemberException
    - FullyQualifiedErrorId : Modules_InvalidManifest,Microsoft.PowerShell.Commands.ImportModuleCommand
    

Environment data

PS /> echo $PSVersionTable

Name Value


PSVersion 6.0.0-alpha
PSEdition Core
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 3.0.0.0
GitCommitId v6.0.0-alpha.9
CLRVersion
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-AnsweredThe question is answered.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions