-
Notifications
You must be signed in to change notification settings - Fork 3.4k
az vm update failed with 'Enabling zone movement' with unrelated action #33500
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 teamBreaking ChangeComputeaz vm/vmss/image/disk/snapshotaz vm/vmss/image/disk/snapshotact-observability-squadcustomer-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
Milestone
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 teamBreaking ChangeComputeaz vm/vmss/image/disk/snapshotaz vm/vmss/image/disk/snapshotact-observability-squadcustomer-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
Type
Fields
Give feedbackNo fields configured for issues without a type.
Describe the bug
When trying to run a
az vm update --set tagscommand it failed with an unrelated 'zone movement' errorRelated command
az vm update
Errors
Issue script & Debug output
above error
Expected behavior
Expect az vm update commands to function and not fail related to an unspecified flag
Environment Summary
azure-cli 2.87.0
Additional context
This does not occur on the previous version 2.86, only on the latest 2.87. Wondering if some cli flag got set regarding zone movement so it tries to update on every update command, even those that don't specify it, and the region doesn't support that feature. This seems to break
az vm updatecommands for me.