Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VM resizing does not take into account settings for Physical / Virtual CPU or Memory Modification settings, as per the VM Template #6875

Open
3 tasks
jimfreeman opened this issue Jan 27, 2025 · 0 comments

Comments

@jimfreeman
Copy link

/!\ 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

Image
Image
Image

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant