hsato03 opened a new pull request, #8894: URL: https://github.com/apache/cloudstack/pull/8894
### Description In a situation where there is a stopped user VM and this VM's network VR is also stopped, starting the user VM will also cause the VR to start. However, in this situation, the VR is inheriting the user VM's boot settings, causing it to not start when the user VM has the UEFI boot type. Because of this, the inheritance of user VM boot settings has been removed from VR and other boot settings have been defined in their place. ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [X] Bug fix (non-breaking change which fixes an issue) - [ ] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) - [ ] build/CI ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [ ] Minor #### Bug Severity - [ ] BLOCKER - [ ] Critical - [ ] Major - [X] Minor - [ ] Trivial ### Screenshots (if appropriate): ### How Has This Been Tested? I followed the same steps from `How did you try to break this feature and the system with this change?` and verified that the user's VM and VR started correctly. #### How did you try to break this feature and the system with this change? 1. I created an isolated network (`isolated`); 2. I deployed a VM (`test`) using the `isolated` network and started it; 3. After implementing the `isolated` network, I stopped the VM `test` and the VR of the `isolated` network; 4. I added the `UEFI=SECURE` setting to the `test` VM and started it again, causing the `isolated` network VR to start as well; 5. The VR could not start because it had the UEFI boot type. -- 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]
