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
When creating a VM template in Sunstone, it is possible to input a value greater than 100% in the Physical CPU (%) field. This is illogical and could lead to resource misconfigurations.
To Reproduce
Steps to reproduce the behavior:
Open the Sunstone interface.
Create or edit a VM template.
Enter a value greater than 100 in the Physical CPU (%) field.
Save the template and observe that the system accepts the value without any validation error.
Expected behavior
The system should validate input for the Physical CPU (%) field and restrict it to a range between 0 and 100. If a value outside this range is entered, the system should reject it with an appropriate error message.
Details
Affected Component: Sunstone
Hypervisor: KVM 6.10
Version: [Provide the version you are using, e.g., 6.10 or latest development build]
Additional context
Allowing values above 100% may cause unexpected behavior in CPU resource allocation, which is inconsistent with logical usage scenarios. Proper validation should be implemented to prevent such inputs.
The text was updated successfully, but these errors were encountered:
Description
When creating a VM template in Sunstone, it is possible to input a value greater than 100% in the Physical CPU (%) field. This is illogical and could lead to resource misconfigurations.
To Reproduce
Steps to reproduce the behavior:
100
in the Physical CPU (%) field.Expected behavior
The system should validate input for the Physical CPU (%) field and restrict it to a range between
0
and100
. If a value outside this range is entered, the system should reject it with an appropriate error message.Details
Additional context
Allowing values above 100% may cause unexpected behavior in CPU resource allocation, which is inconsistent with logical usage scenarios. Proper validation should be implemented to prevent such inputs.
The text was updated successfully, but these errors were encountered: