Prevent creation of unnecessary multiple pod vms on failure #1842
Assignees
Comments
|
The busy loop in CAA for "create vm" should include an exponential backoff mechanism. Beyond that we don't need any heuristics, IMO. This should be applicable to all cloud providers, busy loops calling CSP apis might lead to rate limits and impact a user's account in unfortunate ways. |
kartikjoshi21
added a commit
to kartikjoshi21/cloud-api-adaptor
that referenced
this issue
May 27, 2024
Add check to verify if podvm image is present Fixes: confidential-containers#1842 Signed-off-by: Kartik Joshi <[email protected]>
kartikjoshi21
added a commit
to kartikjoshi21/cloud-api-adaptor
that referenced
this issue
May 27, 2024
Add check to verify if podvm image is present Fixes: confidential-containers#1842 Signed-off-by: Kartik Joshi <[email protected]>
kartikjoshi21
added a commit
to kartikjoshi21/cloud-api-adaptor
that referenced
this issue
Jun 10, 2024
Delete network interface synchronously if vm creation is failed Fixes: confidential-containers#1842 Signed-off-by: Kartik Joshi <[email protected]>
kartikjoshi21
added a commit
to kartikjoshi21/cloud-api-adaptor
that referenced
this issue
Jun 10, 2024
Delete network interface synchronously if vm creation is failed Fixes: confidential-containers#1842 Signed-off-by: Kartik Joshi <[email protected]>
kartikjoshi21
added a commit
to kartikjoshi21/cloud-api-adaptor
that referenced
this issue
Jun 21, 2024
Delete network interface synchronously if vm creation is failed Fixes: confidential-containers#1842 Signed-off-by: Kartik Joshi <[email protected]>
mkulke
pushed a commit
to mkulke/cloud-api-adaptor
that referenced
this issue
Jul 4, 2024
Delete network interface synchronously if vm creation is failed Fixes: confidential-containers#1842 Signed-off-by: Kartik Joshi <[email protected]>
Vaibhav-Nazare
pushed a commit
to Vaibhav-Nazare/cloud-api-adaptor
that referenced
this issue
Jul 6, 2024
Delete network interface synchronously if vm creation is failed Fixes: confidential-containers#1842 Signed-off-by: Kartik Joshi <[email protected]> Signed-off-by: Vaibhav-Nazare <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The CreateVM api call currently exhibits a continuous retry behavior upon encountering failures during VM creation. This leads to multiple unintended VMs being created in the resource group, even when retries are unnecessary, such as when the image is unavailable. This process persists until available network addresses are exhausted, resulting in unnecessary resource creation and potential network conflicts. This bug is opened to discuss implementing a backoff mechanism to prevent this behavior and ensure more reliable VM creation.
The text was updated successfully, but these errors were encountered: