Disabled Create and Add Volume button for VMs in Error state#10859
Conversation
|
Congratulations on your first Pull Request and welcome to the Apache CloudStack community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md)
|
|
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10859 +/- ##
=============================================
- Coverage 16.40% 3.99% -12.41%
=============================================
Files 5692 401 -5291
Lines 501976 32654 -469322
Branches 60795 5791 -55004
=============================================
- Hits 82369 1306 -81063
+ Misses 410449 31198 -379251
+ Partials 9158 150 -9008
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
UI build: ✔️ |
|
Awesome work, congrats on your first merged pull request! |
…10859) Co-authored-by: erik.silva.scclouds <erik.silva@scclouds.com.br>



Description
When a VM fails to deploy, it remains in
Errorstate. Currently, there is no functionality to recover a VM inErrorstate, therefore, the only option is to create a new VM. However, the optionCreate and Add Volumeis still presented. This PR disables theCreate and Add Volumebutton for VMs inErrorstateTypes of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
I made the following tests, in my local lab:
Errorstate.Volumessection was accessed, the Create and Add Volume button was still enabled.Volumessection was accessed again, the button was successfully disabled.