rosi-shapeblue opened a new issue, #10627:
URL: https://github.com/apache/cloudstack/issues/10627

   ### 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.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 misleading error message about the invalid size. This results 
in a notification banner on the frontend indicating a submission error.
   
   <img width="1435" alt="Image" 
src="https://github.com/user-attachments/assets/3d4927b7-d513-4dd2-9687-09b2e1002531";
 />
   
   ### What to do about it?
   
   
   **Expected Result**
   
   The system should automatically trim spaces from the input field before 
submission, preventing the misleading error message. The size value should be 
considered valid once the space is trimmed, and the volume creation should 
proceed as expected.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to