-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Open
Labels
Compute - VMSSMgmtThis issue is related to a management package.This issue is related to a management package.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.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe 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
Description
Library name and version
Azure.ResourceManager.Compute 1.6.0.0
Describe the bug
Calling UpdateAsync with WaitUntil.Completed is not waiting on long running operation to complete. We see that the operation returns right away
Expected behavior
method call should only return after the vmss LRO has finished.
Actual behavior
method return right away as soon as the operation is accepted but doesn't wait for the LOR to finish
Reproduction Steps
call UpdateAsync with WaitUntil.Completed. We've seen it in scale operations.
you can see our implementation here: https://msazure.visualstudio.com/One/_git/winfab-RP?path=/src/sfmc/SfmcBackendService/Common/AzureClient/SfmcArmClient.cs&version=GBdevelop&_a=contents
```
ArmOperation lro = await virtualMachineScaleSet.UpdateAsync(WaitUntil.Completed, vmssUpdate, cancellationToken);
return lro.Value;
### Environment
_No response_
Metadata
Metadata
Assignees
Labels
Compute - VMSSMgmtThis issue is related to a management package.This issue is related to a management package.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.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe 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