Azure powershell Step hangs


I’m trying to execute a Azure Resource Manager cmdlet using Azure powershell step in Octopus 3.4.0-beta0001 but the step hangs at Importing Azure Resource Manager PowerShell modules. I left it for almost 30 minutes but still it didnt complete. Not sure whats the issue. Could you please help?

Task log

Octopus Server version: 3.4.0-beta.1+Branch.release/3.4.0-beta.1.Sha.db3395fa3d4600de5c010260f2433929015fa5e7
August 9th 2016 10:38:44Verbose
Using account ID 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx’
August 9th 2016 10:39:02Verbose
Octopus Deploy: Calamari.Azure version 3.4.0-beta.1+Branch.develop.Sha.575c36e92bb968be6ef413a7194b363a801a3abd
August 9th 2016 10:39:25Verbose
Name Value
August 9th 2016 10:39:25Verbose

August 9th 2016 10:39:25Verbose
PSVersion 5.0.10586.117
August 9th 2016 10:39:25Verbose
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
August 9th 2016 10:39:25Verbose
BuildVersion 10.0.10586.117
August 9th 2016 10:39:25Verbose
CLRVersion 4.0.30319.42000
August 9th 2016 10:39:25Verbose
WSManStackVersion 3.0
August 9th 2016 10:39:25Verbose
PSRemotingProtocolVersion 2.3
August 9th 2016 10:39:25Verbose
August 9th 2016 10:40:10Verbose
Importing Azure Service Management PowerShell module
August 9th 2016 10:48:33Verbose
Importing Azure Resource Manager PowerShell modules

Hi Hari,

Thanks for getting in touch. We’ve never encountered this before but I have a few suggestions to try to fix it.

  • Have you tried this on the latest Octopus 3.3 release? Or Octopus 3.4 beta 2? This should work fine in the Octopus 3.4 betas but there could be an odd change interfering in the first beta. We’re currently bug bashing 3.4 now and looking to ship it soon.
  • Alternately, you could always try installing the Azure powershell modules locally on your server and then tell Octopus to ignore the bundled modules. More information on this is available at the following URL.

Also, I saw you were running PowerShell 5 but can you tell me what version of Windows Server you are running?

It’s also worth noting that final release of Octopus 3.4 has improved the way we load the powershell modules. We no longer explicitly load the Azure PowerShell modules up front but we simply add the location of the bundled modules to the PsModulePath environment variable. This should improve performance moving forward.




This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.