Skip to content
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

Option to retry failed VM instance deployments #5739

Open
PaulAngus opened this issue Dec 1, 2021 · 2 comments · May be fixed by #6062
Open

Option to retry failed VM instance deployments #5739

PaulAngus opened this issue Dec 1, 2021 · 2 comments · May be fixed by #6062

Comments

@PaulAngus
Copy link
Member

ISSUE TYPE
  • Feature Idea
COMPONENT NAME
UI
CLOUDSTACK VERSION
4.16+
CONFIGURATION

NA

OS / ENVIRONMENT

NA

SUMMARY

When a user deployment fails, user ends up with an instance with has a status of Error

image

They will usually then report it to the CloudStack administrators.
Often the problem is in the backend/infrastructure. The administrators fix the issue and say 'try now'.

It would be a nice touch to be able to 'retry' the instance deployment, rather than have to start again.

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

@DaanHoogland
Copy link
Contributor

If all data from the deployment is still available (and I imagine it is) this should be possible. Not sure if the ui can re-compile the request or if the back-end needs another API for this.

@nvazquez
Copy link
Contributor

nvazquez commented Feb 4, 2022

Thanks @PaulAngus great idea!
@DaanHoogland @PaulAngus IMO it should be back-end handled - once the operation fails, a new work/job must be scheduled after certain configured time with the same parameters as the original job (similar to migration jobs when a host is put into maintenance). Apart from configuring the retry time interval, it could be useful to control the number of retry attempts as well

@nvazquez nvazquez self-assigned this Feb 10, 2022
@nvazquez nvazquez linked a pull request Mar 6, 2022 that will close this issue
12 tasks
@nvazquez nvazquez modified the milestones: 4.17.0.0, 4.18.0.0 Mar 21, 2022
@nvazquez nvazquez modified the milestones: 4.18.0.0, 4.19.0.0 Jan 12, 2023
@shwstppr shwstppr modified the milestones: 4.19.0.0, 4.20.0.0 Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment