Azure Automation: "Checksum for configuration does not match"

DSC
1

I’m using Azure GovCloud and Azure Automation.

I can upload and compile simple DSC Configurations.
I can add Azure VMs as DSC Nodes.

However, DSC Nodes report failures on every run but the first.
Under Reports, Consistency is in Failed state: “Checksum for configuration does not match.”

Am I supposed to do something about Checksums while using Azure Automation?
How can I further debug this?

Thank you!

2

Clint and I are both trying Azure Automation, USGov, but using different servers in different resource groups with different configurations. Similar results:

PS C:\Users\pburkholder> Update-DscConfiguration -Wait -Verbose -Debug
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = PerformRequiredConfigurationChecks,'className' =
MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer MYVM1 with user sid S-1-5-21-203942804-2365848562-3944707112-500.
VERBOSE: [MYVM1]:                            [] Executing Get-Action with configuration (null)'s checksum: .
VERBOSE: [MYVM1]:                            [] Executing Get-Action with configuration 's checksum returned result status: GetConfiguration.
VERBOSE: [MYVM1]:                            [] Checksum is different. LCM will execute GetConfiguration to pull configuration .
VERBOSE: [MYVM1]:                            [] Executing GetConfiguration failed. Configuration  is not pulled.
Checksum for configuration does not match.
    + CategoryInfo          : InvalidResult: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : WebDownloadManagerMismatchChecksum,Microsoft.PowerShell.DesiredStateConfiguration.Commands.GetDscDocumentCommand
    + PSComputerName        : localhost

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 3.735 seconds

It looks to us like the target is telling the AzAutomation that it has a null configuration, then the LCM will run `GetConfiguration`, which makes sense. Except `Executing GetConfiguration failed. Configuration is not pulled.`

We’re following the steps at https://docs.microsoft.com/en-us/azure/automation/automation-dsc-getting-started.

3

Update: It works as advertised in public cloud. Opening support ticket for USGov…