-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compute
Capacity Reservation Group
Delete Fails With no Reservations
#18767
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @avirishuv. Issue DetailsHi, I'm using On-demand Capacity Reservation feature and have found an issue with Delete: When I tries deleting the Capacity Reservation Group shortly after (in fewer than 5 seconds) I delete all the reservations in it, it throws an error of still having nested resource in it. Below is what I tested using
|
hi @oriwolman or @TravisCragg-MSFT would you please take a look at this issue? |
@myc2h6o Does the deletion succeed after several minutes has passed, or does it continue to fail? |
Hi @TravisCragg-MSFT the deletion will succeed after a few seconds. |
@myc2h6o Have you tried doing the same via PowerShell or CLI to see if the behavior is the same? |
@TravisCragg-MSFT I haven't tried PowerShell or CLI, I only tried REST API. |
@TravisCragg-MSFT are you still looking into this issue? |
I am following up with our team to fix this delay, or update the error message to state a wait period. |
@myc2h6o This failure can occur sometimes if the delete of the Capacity Reservations has not fully synced and you call a delete for the group. When calling these programmatically, a small delay between the nested resource delete and the Reservation Group delete should resolve this issue. |
Hi, I'm using On-demand Capacity Reservation feature and have found an issue with Delete: When I tries deleting the Capacity Reservation Group shortly after (in fewer than 5 seconds) I delete all the reservations in it, it throws an error of still having nested resource in it.
Below is what I tested using
Invoke-WebRequest
PowerShell command to make the REST API requests. Because it happens only within a short range, I invoked the DELETE in a batch and used GET to check the result. As can be seen below: in the second GET response,capacityReservations
is already removed from the CapacityReservationGroup, but the subsequent DELETE still cannot delete it. And I'm only able to invoke the DELETE after about 5 seconds.The text was updated successfully, but these errors were encountered: