Deploy module [VirtualMachines] in [WVD] via [WVDServiceConnection] FAILED

[Ohedborg]

Hi Team,

Strange failure here - during the deployment in Devops I have an issues with deploying module [VirtualMachines] in [WVD] via [WVDServiceConnection. Specifically recieve the following issue:

Please Advise

[monkeytreehosting]

I've come across this issue now too - does anyone have any information or progression on this please?

Thanks

[EmilJasinski]

Hi, unfortunately I have the same issue: Maybe it has something to do with this part? (storage account diagnostic profile)

[Ohedborg]

@EmilJasinski - Thought the same - tried changing but no success for me .. May have done it wrong, however.

[EmilJasinski]

@Ohedborg - I tried to comment out/modify some diagnostic storage account values, but without success too - the same error remains.

[monkeytreehosting]

I removed line 951 from the screenshot above entirely and the error still came up referring to 'dummy' so it seems to be a different reference point

[Jushiah]

Hey everyone - I'll file a bug for this. Any additional details you can provide (if any) would help.

[monkeytreehosting]

Thanks @justin-shiah

I don't know if it helps, but the specifics of my deployment were:

• AADDS
• MetaData Region: eastus or westus2
• Region: uksouth

Are there any other specifics I can provide or you think would be needed?

[matstocks]

I'm also having the same issue.

[Jushiah]

Do you receive the same error on the initial deployment? I see from the screenshots that you've attempted to deploy the pipeline multiple times. The error is occurring because boot diagnostics is enabled, even though we have it turned off by default. Have you manually turned boot diagnostics on? The quickest way to get unblocked for this error should be to turn boot diagnostics back off.

There is a bug in the way the code is currently written for the case when boot diagnostics is turned on with empty values, we will work on fixing that.

[monkeytreehosting]

@Jushiah Thanks for confirming and highlighting this.

We get the error when deploying fresh with no editing from the default deployment. (Yes, first initial run) From this it would seem boot diagnostics is enabled by default?

Can you advise where I can set this to disabled?

[Jushiah]

@monkeytreehosting That's very interesting to hear, thanks for the additional info. In your DevOps project, can you go to Repos->Files->Modules->ARM->VirtualMachines->deploy.json and check if defaultValue under "enableBootDiagnostics" is set to false?

[monkeytreehosting]

Hi @Jushiah

Copied below the code from the file you referenced; it does look to be defaulted to false

"enableBootDiagnostics": { "type": "bool", "defaultValue": false, "metadata": { "description": "Optional. Whether boot diagnostics should be enabled on the Virtual Machine." } }, "bootDiagnosticStorageAccountName": { "type": "string", "defaultValue": "", "metadata": { "description": "Optional. Storage account used to store boot diagnostic information." } }, "diagnosticLogsRetentionInDays": { "type": "int", "defaultValue": 365, "minValue": 0, "maxValue": 365, "metadata": { "description": "Optional. Specifies the number of days that logs will be kept for; a value of 0 will retain data indefinitely." } }, "diagnosticStorageAccountId": { "type": "string", "defaultValue": "", "metadata": { "description": "Optional. Resource identifier of the Diagnostic Storage Account." } },

[Jushiah]

@monkeytreehosting Thanks! Let me investigate a bit further and I'll circle back with you.

[monkeytreehosting]

@Jushiah Thanks!

[monkeytreehosting]

@Jushiah So I think i've solved or made a work around, If we hardcode the boot storage into "/QS-WVD/static/templates/pipelineInput/wvdsessionhost.parameters.template.json"

    "bootDiagnosticStorageAccountName": {
        "value": "[wvdAssetsStorage]"
    },

This seems to assign the value expected (which we can see in the wvdsessionhost.parameters storage on creating the pipeline), but never actually enables the DiagnosticStorage. Currently still running "Deploy module [VirtualMachines] in [WVD] via [WVDServiceConnection]" - as its waiting for the Deployment on Azure to complete. However - its been running for c. 32 mins at the point of typing this - the error usually comes in at the beginning and doesn't usually get as far as creating a deployment on Azure.

Will report back when the process finishes....

[monkeytreehosting]

So this looks like it would work, but presents a further issue down the line with the CSE Scripts. After 90mins (time out value of the CSE) - we get the auto timeout error. The DevOps Pipeline times out at around 1hr 10mins as no response from Hosted Agent.

[Jushiah]

Hey all - this error should be fixed now, please let me know if you're still running into this issue.

[jerwalla5]

I'm seeing an error in deploy module [virtual machines] as well, but with 'MultipleErrorsOccurred'