-
Notifications
You must be signed in to change notification settings - Fork 3.4k
az vm create --no-wait fails with "Extra data: line 1 column 4 (char 3)" #33152
Copy link
Copy link
Open
Labels
Auto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamComputeaz vm/vmss/image/disk/snapshotaz vm/vmss/image/disk/snapshotact-observability-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Metadata
Metadata
Assignees
Labels
Auto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamComputeaz vm/vmss/image/disk/snapshotaz vm/vmss/image/disk/snapshotact-observability-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Describe the bug
Since yesterday (April 7, 2026),
az vm create --no-waitfails with:This is a JSON parsing error, most likely in the LRO continuation token handling introduced by the pickle-to-JSON migration in
azure-core1.38.0.I can confirm that:
(tested in GH CI environment, on default Ubuntu runner)
The continuation token format was changed from pickle to JSON in
azure-core1.38.0 (Azure/azure-sdk-for-python#44574). A follow-up PR added azure-asyncoperation header handling in azure-mgmt-core (Azure/azure-sdk-for-python#44658).Related command
Errors
Issue script & Debug output
Expected behavior
Command works.
Environment Summary
Additional context
The same CLI version (2.84.0, pre-installed on GitHub Actions runner image) worked on April 2 and broke on April 7, pointing to a server-side change exposing the bug.
Pinning
azure-clito 2.82.0 (last version using azure-core 1.37.0) helped as a workaround.