Failed to deploy new service to Azure, but release didn't fail

Legacy Uncategorised
1

I have a release with 2 steps. The first step was successful, but the second got an error. Yet the release was flagged as successful. Here’s the output of the failing step:

2013-11-21 23:43:38 DEBUG Extracting package to temporary directory: C:\Octopus\Data\tmp\deployments-161
2013-11-21 23:43:38 DEBUG Package extracted successfully
2013-11-21 23:43:38 INFO [XML Transformation] Looking for any configuration transformation files
2013-11-21 23:43:38 INFO [XML Configuration] Looking for appSettings and connectionStrings in any .config files
2013-11-21 23:43:38 DEBUG [Azure Configuration] Azure service configuration file not found: C:\Octopus\Data\tmp\deployments-161\ServiceConfiguration.Dev.cscfg
2013-11-21 23:43:38 DEBUG [Azure Configuration] Found Azure service configuration file: C:\Octopus\Data\tmp\deployments-161\ServiceConfiguration.Cloud.cscfg
2013-11-21 23:43:38 DEBUG [Azure Configuration] Updating configuration settings…
2013-11-21 23:43:38 INFO [Azure Upload] Uploading package to Azure blob storage: C:\Octopus\Data\tmp\deployments-161\AzureHost.cspkg
2013-11-21 23:43:38 DEBUG [Azure Upload] Connecting to Azure blob storage
2013-11-21 23:43:40 INFO [Azure Upload] Package upload complete
2013-11-21 23:43:40 INFO [Azure Upload] Package uploaded as: https://xxxxxxxxx.blob.core.windows.net/octopuspackages/AzureHost.1.0.0.123_75b4b3dab514e8946097871853fb900ab335b0e9.cspkg
2013-11-21 23:43:40 DEBUG [Azure Deployment] Script: C:\Octopus\Data\tmp\deployments-161\BootstrapDeployToAzure.ps1
2013-11-21 23:43:41 INFO [Azure Deployment] Azure deployment parameters:
2013-11-21 23:43:41 INFO [Azure Deployment] Subscription ID: xxxxxxxxxxxxxxxxxxxxxxxx
2013-11-21 23:43:41 INFO [Azure Deployment] Subscription name: xxxxxxxxxxxxxxxxxxxxxxxxx
2013-11-21 23:43:41 INFO [Azure Deployment] Cloud service name: xxxxx-portal-web-dev
2013-11-21 23:43:41 INFO [Azure Deployment] Storage account name: xxxxxx
2013-11-21 23:43:41 INFO [Azure Deployment] Slot: Production
2013-11-21 23:43:41 INFO [Azure Deployment] Package URI: https://xxxxxxx.blob.core.windows.net/octopuspackages/AzureHost.1.0.0.123_75b4b3dab514e8946097871853fb900ab335b0e9.cspkg
2013-11-21 23:43:41 INFO [Azure Deployment] Configuration file: C:\Octopus\Data\tmp\deployments-161\ServiceConfiguration.Cloud.cscfg
2013-11-21 23:43:41 INFO [Azure Deployment] Deployment label: Deploy Portal/Web v1.0.0.123
2013-11-21 23:43:41 INFO [Azure Deployment] Allow swap: False
2013-11-21 23:43:41 INFO [Azure Deployment] Importing Windows Azure modules
2013-11-21 23:43:41 INFO [Azure Deployment] Loading the management certificate
2013-11-21 23:43:41 INFO [Azure Deployment] Setting up the Azure subscription
2013-11-21 23:43:41 INFO [Azure Deployment] Starting the Azure deployment process
2013-11-21 23:43:42 INFO [Azure Deployment] Creating a new deployment…
2013-11-21 23:43:43 INFO [Azure Deployment] WARNING: The default subscription is being removed. Use Select-Subscription
2013-11-21 23:43:43 INFO [Azure Deployment] to select a new default subscription.
2013-11-21 23:43:43 INFO [Azure Deployment] WARNING: The current subscription is being removed. Use Select-Subscription
2013-11-21 23:43:43 INFO [Azure Deployment] to select a new current subscription.
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: New-AzureDeployment : "An exception occurred when calling the
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: ServiceManagement API. HTTP Status Code: 404. Service Management Error Code:
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: ResourceNotFound. Message: The hosted service does not exist… Operation
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: Tracking ID: fa37c7482b8f3d25b21f0bfd83cf0ba8."
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: At C:\Octopus\Data\tmp\deployments-161\DeployToAzure.ps1:73 char:5
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: + New-AzureDeployment -Slot $OctopusAzureSlot -Package
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: $OctopusAzurePackageUri …
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: ~~~
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: + CategoryInfo : CloseError: (:slight_smile: [New-AzureDeployment], ServiceMa
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: nagementClientException
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: + FullyQualifiedErrorId : Microsoft.WindowsAzure.Management.ServiceManagem
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR: ent.HostedServices.NewAzureDeploymentCommand
2013-11-21 23:43:44 INFO [Azure Deployment] ERROR:
2013-11-21 23:43:44 WARN [Azure Deployment] The script returned an exit code of 0, but output was written to the error output stream. Please investigate any errors in the script output above.
2013-11-21 23:43:44 DEBUG Deleting temporary directory C:\Octopus\Data\tmp\deployments-161

2

Hi,

Thanks for reporting this. This is partly due to how we invoke PowerShell and exit codes not being returned properly. We think we’ve fixed this once and for all in Octopus 2.0.

Paul

3

Paul,

Thanks for the reply. Any chance we can get on the 2.0 beta? We have a new product using Octopus and it’s not mission critical yet (still build-out) so we can take some bugs.

Thanks,
/Hakan

4

Sure, you can download the beta here:

Paul

5

Ah, very good, thanks. I just read there’s no octo.exe/TC plugin, is there a doc on how I would trigger the deployment from TeamCity in 2.0?

/Hakan

6

For now it isn’t possible but we should have a new build of octo.exe/TC
plugin that is compatible with 2.0 by the end of this week.

Regards,

Paul Stovell
Octopus Deploy
W: octopusdeploy.com | T: @octopusdeploy http://twitter.com/octopusdeploy

7

Ok, I’ll hold off until the Turkey is eaten then :slight_smile:

Thanks,
/Hakan