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

Trailing Spaces in Size Input Fields Cause Submission Error #10627

Open
rosi-shapeblue opened this issue Mar 27, 2025 · 1 comment · May be fixed by #10629
Open

Trailing Spaces in Size Input Fields Cause Submission Error #10627

rosi-shapeblue opened this issue Mar 27, 2025 · 1 comment · May be fixed by #10629
Milestone

Comments

@rosi-shapeblue
Copy link

rosi-shapeblue commented Mar 27, 2025

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

  1. Navigate to Storage -> Volumes -> Create volume
  2. Add new Volume
  3. Select "Custom disk offering" -> fill in all mandatory fields
  4. In the Size input field -> enter a value with a trailing space, e.g., "10 " (without quotes).
  5. Submit the form

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.

Image

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.

Copy link

boring-cyborg bot commented Mar 27, 2025

Thanks for opening your first issue here! Be sure to follow the issue template!

@DaanHoogland DaanHoogland self-assigned this Mar 27, 2025
@DaanHoogland DaanHoogland added this to the 4.19.3 milestone Mar 27, 2025
@DaanHoogland DaanHoogland removed their assignment Mar 27, 2025
@DaanHoogland DaanHoogland linked a pull request Mar 27, 2025 that will close this issue
14 tasks
@weizhouapache weizhouapache linked a pull request Mar 28, 2025 that will close this issue
14 tasks
@DaanHoogland DaanHoogland moved this from Todo to ready for Review in Apache CloudStack BugFest - Issues Apr 8, 2025
@DaanHoogland DaanHoogland moved this from ready for Review to ready for Testing in Apache CloudStack BugFest - Issues Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ready for Testing
Development

Successfully merging a pull request may close this issue.

2 participants