Investigate build error - BuildHelpers Set-ModuleFunctions

[adamrushuk]

https://ci.appveyor.com/project/adamrushuk/psvcloud/build/0.2.0.23

Executing Build

Error: 5/21/2017 4:02:12 PM:

•         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [<<==>>] Exception: Could not find module 'C:\projects\psvcloud\psvcloud\psvcloud.psd1'
  

Command executed with exception: Could not find module 'C:\projects\psvcloud\psvcloud\psvcloud.psd1'

===

Issue exists in "C:\Program Files\WindowsPowerShell\Modules\BuildHelpers\0.0.45\Public\Set-ModuleFunctions.ps1":

Could not find module 'PSvCloud.psd1'
At TestImport.ps1:32 char:5

• Throw "Could not find module '$Name'"
  

• ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : OperationStopped: (Could not find ...\PSvCloud.psd1':String) [], RuntimeException
  • FullyQualifiedErrorId : Could not find module 'PSvCloud.psd1'

===

I suspect this may be due to a PowerCLI issue with Runspaces, and this known error on subsequent loading of PowerCLI (the first import-module is successful):

Import-Module : The specified mount name 'vis' is already in use.
At line:1 char:5

• Import-Module -Name $Name -PassThru:$Passthru -Force:$Force
  

• ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidOperation: (:) [Import-Module], DriveException
  • FullyQualifiedErrorId : NewDriveProviderException,Microsoft.PowerShell.Commands.ImportModuleCommand

Check: https://communities.vmware.com/thread/513253?start=0&tstart=0

[adamrushuk]

This worked when I removed vCloud Module from RequiredModules in .psd1 file.

[adamrushuk]

TODO: Report this issue to VMware PowerCLI team.