erikbocks opened a new pull request, #10859:
URL: https://github.com/apache/cloudstack/pull/10859

   ### Description
   
   When a VM fails to deploy, it remains in `Error` state. Currently, there is 
no functionality to recover a VM in `Error` state, therefore, the only option 
is to create a new VM. However, the option `Create and Add Volume` is still 
presented. This PR disables the `Create and Add Volume`  button for VMs in 
`Error` state
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [X] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] build/CI
   - [ ] test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [X] Minor
   
   ### Screenshots (if appropriate):
   
   
![image](https://github.com/user-attachments/assets/e316a851-5938-46ab-9e4c-a2d778222ee5)
   
   ### How Has This Been Tested?
   
   I made the following tests, in my local lab:
   
   1. Disabled all the hosts in my environment.
   2. Tried to deploy a new VM. As expected, the deploy failed and it was set 
to `Error` state.
   3. Validated that when the `Volumes` section was accessed, the Create and 
Add Volume button was still enabled.
   4. Built and installed CloudStack's packages with my fix. 
   5. Validated that when the `Volumes` section was accessed again, the button 
was successfully disabled.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to