Last two weeks I quite often get this error during deploy to Azure Cloud Services:
It’s appeared for few services in two locations (West Europe and East US). Octopus version 3.11.12
After retry usually deploy success.
I’ve never seen it before, I suspect that this may be due to a new version of the octopus.
09:56:54 Verbose | Uploading package to blob storage: 149.132 MB of 149.132 MB
09:56:54 Verbose | Upload complete
09:56:54 Info | Package upload complete
09:56:54 Info | Package uploaded to https://storagename.blob.core.windows.net/octopuspackages/AzureCloudService.20.94-test_19fd1df273c16944315847d80aa05b0aa6106cfc.cspkg
09:56:54 Info | Config file: C:\Octopus\Work\20170324095307-298\staging\ServiceConfiguration.Production.cscfg
09:56:54 Verbose | Loading certificate with thumbprint: 64A6468E3D7D95B6ADF18FDC10
09:56:54 Verbose | Certificate was found in store
09:56:54 Verbose | Name Value
09:56:54 Verbose | ---- -----
09:56:54 Verbose | PSVersion 4.0
09:56:54 Verbose | WSManStackVersion 3.0
09:56:54 Verbose | SerializationVersion 1.1.0.1
09:56:54 Verbose | CLRVersion 4.0.30319.42000
09:56:54 Verbose | BuildVersion 6.3.9600.17400
09:56:54 Verbose | PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
09:56:54 Verbose | PSRemotingProtocolVersion 2.2
09:56:55 Verbose | PowerShell Environment Information:
09:56:55 Verbose | OperatingSystem: Microsoft Windows NT 6.3.9600.0
09:56:55 Verbose | OsBitVersion: x64
09:56:55 Verbose | Is64BitProcess: True
09:56:55 Verbose | CurrentUser: NT AUTHORITY\SYSTEM
09:56:55 Verbose | MachineName: OCTOPUS
09:56:55 Verbose | ProcessorCount: 2
09:56:55 Verbose | CurrentDirectory: C:\Octopus\Work\20170324095307-298\staging
09:56:55 Verbose | CurrentLocation: C:\Octopus\Work\20170324095307-298\staging
09:56:55 Verbose | TempDirectory: C:\Windows\TEMP
09:56:55 Verbose | HostProcessName: powershell
09:56:55 Verbose | TotalPhysicalMemory: 7339572 KB
09:56:55 Verbose | AvailablePhysicalMemory: 5225664 KB
09:56:55 Verbose | Adding bundled Azure PowerShell modules to PSModulePath
09:56:55 Verbose | Loading the management certificate
09:56:56 Verbose | Invoking target script “C:\Octopus\Work\20170324095307-298\staging\DeployToAzure.ps1” with parameters
09:57:01 Verbose | A deployment already exists in deployEastUs for slot Production. Upgrading deployment…
10:03:07 Error | Set-AzureDeployment : InternalError : The server encountered an internal
10:03:07 Error | error. Please retry the request.
10:03:07 Error | At C:\Octopus\Work\20170324095307-298\staging\DeployToAzure.ps1:42 char:5
10:03:07 Error | + Set-AzureDeployment -Upgrade -ServiceName $OctopusAzureServiceName
10:03:07 Error | -Package …
10:03:07 Error | + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10:03:07 Error | ~~~
10:03:07 Error | + CategoryInfo : CloseError: (
[Set-AzureDeployment], ComputeCl
10:03:07 Error | oudException
10:03:07 Error | + FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagemen
10:03:07 Error | t.HostedServices.SetAzureDeploymentCommand
10:03:07 Error | Script ‘C:\Octopus\Work\20170324095307-298\staging\DeployToAzure.ps1’ returned non-zero exit code: 1
10:03:07 Error | Running rollback conventions…
10:03:07 Error | Script ‘C:\Octopus\Work\20170324095307-298\staging\DeployToAzure.ps1’ returned non-zero exit code: 1
10:03:10 Verbose | Updating manifest with output variables
10:03:10 Fatal | The remote script failed with exit code 1