az desktopvirtualization with error "Cannot deserialize datetime object., ValueError: Invalid datetime string"

[eliasarellano]

This is autogenerated. Please review and update as needed.

Describe the bug

From yesterday March 17th along the day, I had an issue that I have never encountered before, even the script that executes this has not been modified since 8 months ago.

In the script I generate a token for the WVD (also called AWD today) hostpool in order to provide the token to the virtual machine that will handle RD WEB multisession service.

The script executes the 2 following commands:
`$expiration_token_date = (Get-Date).AddDays(20).ToString("yyyy-MM-dTHH:mm:ss.fffffffZ")

az desktopvirtualization hostpool update --registration-info expiration-time="$($expiration_token_date)" registration-token-operation="Update" --name "$($ExistingWVDHostPoolName)" --resource-group "$($ResourceGroupName)" --debug

`

In summary, in order to generate the WVD hostpool token, I need the expiration date. Unfortunately, now this execution says

msrest.exceptions.SerializationError: Unable to build a model: Cannot deserialize datetime object., ValueError: Invalid datetime string: 2022-04-7T11:48:30.0072006Z, DeserializationError: Cannot deserialize datetime object., ValueError: Invalid datetime string: 2022-04-7T11:48:30.0072006Z

It was working well before, now it is even blocking the deployment of the WVD in production automatically. Actually we use Azure pipelines, and obviously it has been tested in azure cloud shell too.

The data time and the command have been inspired from the example of that official documentation : https://docs.microsoft.com/fr-fr/cli/azure/desktopvirtualization/hostpool?view=azure-cli-latest

I'll put the logs here attached

Command Name
az desktopvirtualization hostpool update

Errors:

msrest.exceptions.SerializationError: Unable to build a model: Cannot deserialize datetime object., ValueError: Invalid datetime string: 2022-04-7T11:48:30.0072006Z, DeserializationError: Cannot deserialize datetime object., ValueError: Invalid datetime string: 2022-04-7T11:48:30.0072006Z

To Reproduce:

Create a WVD hostpool in the resource group, with the workspace and the WVD app, then execute the 2 commands lines that are provided to generate the token in the hostpool.

• Put any pre-requisite steps here...
• az desktopvirtualization hostpool update {} --name {} --resource-group {}

Expected Behavior

Gnerated token without issues, the token should be used to paste it in the WVD agent bootloader in the virtual machine automatically.

Environment Summary

Azure cloud shell , also in Agent self hosted.
Python 3.8.12
Installer: DEB

azure-cli 2.34.1

Extensions:
desktopvirtualization 0.1.0
azure-devops 0.22.0
account 0.2.1
ai-examples 0.2.5
ssh 1.0.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

az_desktopvirtualization_bug.txt

[yonzhan]

desktopvirtualization

[eliasarellano]

any tips for that ?

[wangzelin007]

@eliasarellano,

$expiration_token_date = (Get-Date).AddDays(10).ToString("yyyy-MM-dTHH:mm:ss.fffffffZ")
2022-04-2T17:07:47.6184009Z
$expiration_token_date = (Get-Date).AddDays(10).ToString("yyyy-MM-ddTHH:mm:ss.fffffffZ")
2022-04-02T17:07:55.8430639Z
I think you miss a d in your expiration_token_date, So the date formate is also miss a zero sometimes.

[eliasarellano]

@eliasarellano,

$expiration_token_date = (Get-Date).AddDays(10).ToString("yyyy-MM-dTHH:mm:ss.fffffffZ")
2022-04-2T17:07:47.6184009Z
$expiration_token_date = (Get-Date).AddDays(10).ToString("yyyy-MM-ddTHH:mm:ss.fffffffZ")
2022-04-02T17:07:55.8430639Z
I think you miss a d in your expiration_token_date, So the date formate is also miss a zero sometimes.

Hello everyone !

Interesting. that could even mean that everytime that I deployed a project it was always giving dates from 10 to 31, but never from 1 to 9, just lucky.

I will make some tests today and tomorrow , and I will add this 'd' character in the format, then I will let you know :) , thank you so much !

My last question, do you suggest to use all the AZ CLI commands in production? or in this case I should go back to Azure powershell, in fact everytime when I execute this I have the following message :

"WARNING: Command group 'desktopvirtualization hostpool' is experimental and under development. Reference and support levels: https://aka.ms/CLI_refstatus"

What could be your suggestion?

[wangzelin007]

Hi eliasarellano,

We are going to release a new version of desktopvirtualization at 2022/04/06.
It will use the latest stable version (2021-07-12) of desktopvirtualization sdk.
And actually Azure CLI and Azure powershell use the same sdk.
Experimental and preview means change in response to customer feedback.
GA is permanent.
I think you can use all the Azure CLI commands in production.
But if you want avoid most breaking change, you can choose to use all GA commands in Azure CLI.