Hi,
We are testing the water for Azure Cloud Services, and have been playing around with getting OctopusDeploy to actually release to Azure. We are having some frustrations, that may be of our own doing - but we can’t tell!
Firstly we are running with OctopusDeploy 2.6.4.951, and are using the built in Azure deployment step. We have a Tentacle installed on our OctopusDeploy server that we are using, and have uploaded the certificate to the Management Certificates in settings.
It looks like we have a similar problem to this post (http://help.octopusdeploy.com/discussions/problems/16655-azure-cloudservice-deployment) and also this post (http://help.octopusdeploy.com/discussions/problems/9178-storage-exception-during-azure-deployment) however I can confirm we have uploaded the certificate to the right location, and a restart of the Octopus server did not help matters
As we have gone through this debugging process we have double checked the subscription ID is correct, that the other properties are correct.
Any help is greatly appreciated, we are going a little mad here!
Hi Rich,
Thanks for getting in touch! Can you give details for the problems that you are seeing please. What errors are you actually seeing, what problem are you having apart from ‘having frustrations’? Because I am not sure how to help.
Is it in your setup, can you deploy, is it a deployment error, is it pre-deployment… Any more detail you can provide would help.
Thanks!
Vanessa
Hi Vanessa,
The error that we are getting is as follows (with the log attached also):
Uploading package to Azure blob storage: C:\Octopus\Applications\Orbis Challenge Azure\ExampleCloudService\0.1.0.80_8\ExampleCloudService.ccproj.cspkg
Fatal 18:30:12
“An exception occurred when calling the ServiceManagement API. HTTP Status Code: 403. Service Management Error Code: ForbiddenError. Message: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription… Operation Tracking ID: .”
Microsoft.WindowsAzure.ServiceManagement.ServiceManagementClientException: “An exception occurred when calling the ServiceManagement API. HTTP Status Code: 403. Service Management Error Code: ForbiddenError. Message: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription… Operation Tracking ID: .”
at Microsoft.WindowsAzure.ServiceManagement.ServiceManagementChannelProxy.GetRestFaultFromComEx(CommunicationException cex)
at Microsoft.WindowsAzure.ServiceManagement.ServiceManagementChannelProxy.Invoke(IMessage msg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.WindowsAzure.ServiceManagement.IServiceManagement.EndGetStorageKeys(IAsyncResult asyncResult)
at Octopus.Tentacle.Integration.Azure.AzurePackageUploader.Upload(SubscriptionData subscription, String packageFile, String uploadedFileName, ILog log, CancellationToken cancellation) in y:\work\refs\heads\master\source\Octopus.Tentacle\Integration\Azure\AzurePackageUploader.cs:line 27
at Octopus.Tentacle.Procedures.Implementations.Azure.AzureUploadProcedure.UploadPackage(ProcedureState state, CancellationToken cancellationToken) in y:\work\refs\heads\master\source\Octopus.Tentacle\Procedures\Implementations\Azure\AzureUploadProcedure.cs:line 55
at Pipefish.Async.CaptiveThread1.ThreadAction(Action2 action, Guid operationId, IActivitySpace space, Guid captiveThreadId) in y:\work\3cbe05672d69a231\source\Pipefish\Async\CaptiveThread.cs:line 114
Tentacle version 2.6.4.951
Cheers
Rich
ServerTasks-41385.log.txt (8 KB)
Hi Rich,
This error is really only seen when the details or certs are incorrect. Did you create a new release after any changes were made and everything was double checked?
Vanessa