-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Trailing Spaces in Size Input Fields Cause Submission Error #10627
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
Labels
Milestone
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
14 tasks
14 tasks
shwstppr
added a commit
to shapeblue/cloudstack
that referenced
this issue
Apr 16, 2025
Fixes apache#10627 Signed-off-by: Abhishek Kumar <[email protected]>
14 tasks
@rosi-shapeblue @weizhouapache @DaanHoogland I've created #10737 which should address this across UI |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
problem
Description
When selecting a custom disk offering while creating a new volume or VM in CloudStack, entering a size value with a trailing space (e.g., "10 ") causes the API to fail with the error message "Unable to execute API command createVolume due to invalid value 10 for parameter size".
The error message is misleading because the value itself is actually valid, but the system does not automatically trim the trailing space, causing the failure. This results in a submission error when the system attempts to process the request.
versions
CloudStack 4.19.0.2
CloudStack 4.20.0.0
The steps to reproduce the bug
Actual Result
The size field includes a trailing space, causing the backend to reject the request with the error message about the invalid size. This results in a notification banner on the frontend indicating a submission error.
What to do about it?
Expected Result
The system should automatically trim spaces from the input field before submission, preventing the error message. The size value should be considered valid once the space is trimmed, and the volume creation should proceed as expected.
The text was updated successfully, but these errors were encountered: