Add retry mechanism for Azure VM update API concurrent request conflicts #4216
+47
−16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
begin_updatecalls that need retry mechanismbegin_updatecalls in theresizemethodbegin_updatecalls in theattach_nicsmethodbegin_updatecalls in theremove_extra_nicsmethodSummary
Added retry mechanism to handle Azure
ResourceExistsError(Conflict) errors when concurrent requests are made to VM update APIs. Created helper methods with@retrydecorator (5 tries, 2s delay, 1.5x backoff) for:Resize._update_vm_size()- VM resize operationsNetworkInterface._update_vm_nics()- Network interface attach/remove operationsAll changes follow existing codebase patterns and are minimal in scope.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.