You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/!\ To report a security issue please follow this procedure:
[https://github.com/OpenNebula/one/wiki/Vulnerability-Management-Process]
Description
VM resizing does not take into account settings for Physical / Virtual CPU or Memory Modification settings, as per the VM Template
To Reproduce
Download an App from the OpenNebula Marketplace
Edit the VM template and add Memory or CPU Modification to Range or List
Build a VM from these Template
Click Resize VM on the VM page
When you change the resources in the VM, it is not confined by the Modification settings as per the VM template
Expected behavior
When Reizing the VM it should take into account the same CPU/Memory Modification rules as per what is set in the VM Template
Details
Affected Component: Sunstone
Hypervisor: KVM
Version: 6.10.2
Additional context
Find attached images of the VM template settings, what you see when you build a VM, and what you see when you go to resize a VM from the same template
Progress Status
Code committed
Testing - QA
Documentation (Release notes - resolved issues, compatibility, known issues)
The text was updated successfully, but these errors were encountered:
/!\ To report a security issue please follow this procedure:
[https://github.com/OpenNebula/one/wiki/Vulnerability-Management-Process]
Description
VM resizing does not take into account settings for Physical / Virtual CPU or Memory Modification settings, as per the VM Template
To Reproduce
Expected behavior
When Reizing the VM it should take into account the same CPU/Memory Modification rules as per what is set in the VM Template
Details
Additional context
Find attached images of the VM template settings, what you see when you build a VM, and what you see when you go to resize a VM from the same template
Progress Status
The text was updated successfully, but these errors were encountered: