Calling Set-AzureServiceDiagnosticsExtension with -Role failing

[craig-wagner]

Based on the version number showing in "Programs and Features" I'm running 0.9.1 of the Azure Powershell. I installed it yesterday (2015/05/13) using the Web Platform Installer.

$storage_name = "mystorageaccountname"
$key = "mykey"
$service_name = "cwagner-ipseity-worker"
$public_config = "C:\tfs\SI\ipseity\trunk\BuildArtifacts\Deployment\Packages\AzureWorker\PaaSDiagnostics.Ipseity.Server.MessageProcessor.AzureWorkerRole.PubConfig.xml" 
$storageContext = New-AzureStorageContext -StorageAccountName $storage_name -StorageAccountKey $key
Set-AzureServiceDiagnosticsExtension -StorageContext $storageContext -DiagnosticsConfigurationPath $public_config -ServiceName $service_name -Slot Production -Role Ipseity.Server.MessageProcessor.AzureWorkerRole

I get the following output:

VERBOSE: Setting PaaSDiagnostics configuration for Ipseity.Server.MessageProcessor.AzureWorkerRole.
Set-AzureServiceDiagnosticsExtension : BadRequest: The extension ID
IpseityServerMessageProcessorAzureWorkerRole-PaaSDiagnostics-Production-Ext-0 is invalid.
At line:1 char:1

• Set-AzureServiceDiagnosticsExtension -StorageContext $storgeContext -Diagnostics ...

• • CategoryInfo : NotSpecified: (:) [Set-AzureServiceDiagnosticsExtension], CloudException
  • FullyQualifiedErrorId : Hyak.Common.CloudException,Microsoft.WindowsAzure.Commands.ServiceManagement.Extensions.
    SetAzureServiceDiagnosticsExtensionCommand

I realize this is similar to #72 (dots in the role name) but it is my understanding that that issue has been fixed and the reported extension ID in error has had the dots stripped.

If we don't specify the -Role parameter it works.

[devigned]

@matt-gibbs or @markcowl thoughts on this one?

[bgambs]

Similar issue here;

 $setdeployment = Set-AzureDeployment -Upgrade -Slot $slot -Package $packageLocation -Configuration $cloudConfigLocation -label $deploymentLabel -ServiceName $serviceName -Force -ExtensionConfiguration @($workerDiagConfig,$webDiagConfig)

yields

BadRequest: The extension ID FixxxxxxWorkerRoleCommandProcessor-PaaSDiagnostics-Production-Ext-0 is invalid.

We don't have a full stack trace yet, because Jenkins, but

+ CategoryInfo          : NotSpecified: (:) [Set-AzureDeployment], CloudException
+ FullyQualifiedErrorId : Hyak.Common.CloudException,Microsoft.WindowsAzure.Commands.ServiceManagement.HostedServices.SetAzureDeploymentCommand

[bgambs]

@craig-wagner @devigned We managed to resolve this particular issue - by shortening the name of the worker role. No idea what the limit is but FixxxxxxWorkerRoleCommandProcessor is too long and FixxxxxxWorker is not.

[singhkays]

@huangpf Can you take a look at why long worker role names are causing this? Thanks!

[ToonDC]

@huangpf Info: having the same issue also in 0.9.3.

[huangpf]

@ToonDC
Does the problem occur in Set-AzureDeployment, Set-AzureServiceDiagnosticsExtension, or both?

Do you have the repro steps, operation IDs, logs, etc?

[ToonDC]

I have it for both + also for New-AzureDeployment, I created a sample project that you can find here code on github.

1. Publish the solution via Visual Studio 2013 Update 4 and notice that that works as expected.
2. Execute the script New-AzureDeployment.ps1
3. Same for the script Set-AzureDeployment.ps1
4. Same for the script Set-AzureServiceDiagnosticsExtension.ps1
5. View (my) output on the screenshot (CLI version is also visible on the top of the script.

If you are not able to reproduce I would like to provide the operation IDs, etc.

[huangpf]

@ToonDC Thanks for the information. It does reproduce.

Is it feasible for you to use a shorter role name, like $azureWebRoleName = "WebRole1"? One our end, we need to triage and come up with a better solution to handle the recent extension ID-related issues. Assign it back to @singhkay for creating an item for triage and tracking.

@craig-wagner
This is a different issue than #72 in that here the validation is about the length of the extension ID.

[ToonDC]

@huangpf it is feasible to rename the web/workerroles, but it's far from ideal.

[huangpf]

@ToonDC Sorry for the inconvenience. This is just a temporary mitigation for now.

We would try to come up with a better and more generic solution for the extension ID-related issues.

Thanks.

[craig-wagner]

@huangpf Thanks. I realized it was a different issue. I only put the reference to #72 in because they sound very similar (and have the same title) and was trying to avoid someone saying, "That's already been fixed, see #72."