Cloud Service deployment fails with authentication error

Legacy Cloud
1

Hi,
We are using version v2018.9.15.
We have migrated from 3.2.24 where CS deployments worked fine.
I’ve re-created all relevant components:

  • CS target
  • Management certificate accounts
  • Deployment step

It looks like authentication to storage account fails.

Deployments to Cloud Service fails with error:

10:53:23 Verbose | Certificate was found in store 10:53:25 Error | Hyak.Common.CloudException: ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription. 10:53:25 Error | at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) 10:53:25 Error | at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task) 10:53:25 Error | at Microsoft.WindowsAzure.Management.Storage.StorageAccountOperationsExtensions.GetKeys(IStorageAccountOperations operations, String accountName) 10:53:25 Error | at Calamari.Azure.Integration.AzurePackageUploader.GetStorageAccountPrimaryKey(SubscriptionCloudCredentials credentials, String storageAccountName, String serviceManagementEndpoint) 10:53:25 Error | at Calamari.Azure.Integration.AzurePackageUploader.Upload(SubscriptionCloudCredentials credentials, String storageAccountName, String packageFile, String uploadedFileName, String storageEndpointSuffix, String serviceManagementEndpoint) 10:53:25 Error | at Calamari.Azure.Deployment.Conventions.UploadAzureCloudServicePackageConvention.Install(RunningDeployment deployment) 10:53:25 Error | at Calamari.Deployment.ConventionProcessor.RunInstallConventions() 10:53:25 Error | at Calamari.Deployment.ConventionProcessor.RunConventions() 10:53:25 Error | Running rollback conventions… 10:53:25 Error | ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription. 10:53:25 Error | Hyak.Common.CloudException 10:53:25 Error | at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) 10:53:25 Error | at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task) 10:53:25 Error | at Microsoft.WindowsAzure.Management.Storage.StorageAccountOperationsExtensions.GetKeys(IStorageAccountOperations operations, String accountName) 10:53:25 Error | at Calamari.Azure.Integration.AzurePackageUploader.GetStorageAccountPrimaryKey(SubscriptionCloudCredentials credentials, String storageAccountName, String serviceManagementEndpoint) 10:53:25 Error | at Calamari.Azure.Integration.AzurePackageUploader.Upload(SubscriptionCloudCredentials credentials, String storageAccountName, String packageFile, String uploadedFileName, String storageEndpointSuffix, String serviceManagementEndpoint) 10:53:25 Error | at Calamari.Azure.Deployment.Conventions.UploadAzureCloudServicePackageConvention.Install(RunningDeployment deployment) 10:53:25 Error | at Calamari.Deployment.ConventionProcessor.RunInstallConventions() 10:53:25 Error | at Calamari.Deployment.ConventionProcessor.RunConventions() 10:53:25 Error | at Calamari.Azure.Commands.DeployAzureCloudServiceCommand.Execute(String commandLineArguments) 10:53:25 Error | at Calamari.Program.Execute(String args) 10:53:25 Verbose | Process C:\Windows\system32\WindowsPowershell\v1.0\PowerShell.exe in D:\Octopus\Work\20181218094917-279705-13200 exited with code 100

3

Hi Joona,

Thanks for getting in touch.

We were able to reproduce this error and have created an issue here to be investigated with priority.

Unfortunately we’re not aware of any workarounds at this time.

Sorry for the inconvenience. We recommend following that issue above to be notified when a fix is available.

Cheers
Mark

4

Hi again Joona,

Could you please confirm the “Execution Location” that you have configured for your cloud service step?

Is this set to run on the server, or is your instance configured to use Worker Pools?

For example, does the top of your cloud service step look similar to this (in terms of the Execution Location field):

2018-12-20%2013_18_41-Process%20-%20Octopus%20Deploy
2018-12-20 13_18_41-Process - Octopus Deploy.png2077×962 62.3 KB

Or like this:

2018-12-20%2013_19_24-Process%20-%20Octopus%20Deploy
2018-12-20 13_19_24-Process - Octopus Deploy.png1992×492 29.5 KB

Cheers
Mark

5

Hi,
Like this:

image
image.png1463×422 32.1 KB

6

Hi Joona,

We are confident that we now know what caused this problem, have made the necessary fixes and will be releasing the fix as part of 2018.11.2 very shortly. I would like to apologize for the delays in getting this addressed and for any inconvenience this may have caused you.

Regards,
Shaun