You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2021/12/01 10:23:54 UTC

[GitHub] [cloudstack] PaulAngus opened a new issue #5739: Option to retry failed VM instance deployments

PaulAngus opened a new issue #5739:
URL: https://github.com/apache/cloudstack/issues/5739


   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
   
    * Feature Idea
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   UI
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main branch.
   -->
   
   ~~~
   4.16+
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   NA
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   NA
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   When a user deployment fails, user ends up with an instance with has a status of `Error`
   
   ![image](https://user-images.githubusercontent.com/4810220/144216638-99ea0b7e-90d0-4d30-ab10-8f4b17ca33cd.png)
   
   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
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   
   ~~~
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [cloudstack] DaanHoogland commented on issue #5739: Option to retry failed VM instance deployments

Posted by GitBox <gi...@apache.org>.
DaanHoogland commented on issue #5739:
URL: https://github.com/apache/cloudstack/issues/5739#issuecomment-984404666


   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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [cloudstack] nvazquez commented on issue #5739: Option to retry failed VM instance deployments

Posted by GitBox <gi...@apache.org>.
nvazquez commented on issue #5739:
URL: https://github.com/apache/cloudstack/issues/5739#issuecomment-1029561916


   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


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org