rosi-shapeblue commented on PR #11766:
URL: https://github.com/apache/cloudstack/pull/11766#issuecomment-3385560254

   @DaanHoogland , @CodeBleu -  I’ve completed testing this on my test 
environment.
   
   1. Creating a Load Balancer rule with single/multiple CIDRs (e.g. 
1.1.1.1/32,2.2.2.0/24,3.3.3.3/32) **works as expected.**
   
   
   
   2. **Editing** an existing rule and **appending** additional CIDRs **fails** 
with:
   
   _Failed to edit rule
   Invalid CIDR list: 1.1.1.1/32 2.2.2.0/24,3.3.3.3/32_
   
   <img width="3109" height="1623" alt="image" 
src="https://github.com/user-attachments/assets/80728ac8-8b6b-4d98-99ac-ede56aafbbac";
 />
   
   The input was entered correctly (no spaces), but during the edit flow the UI 
alters the CIDR string - a space replaces the first comma between the CIDRs, 
resulting in a malformed value being sent to the backend.
   
   Browser console shows:
   
   _Uncaught (in promise) TypeError: Cannot read properties of undefined 
(reading 'push')
       at LoadBalancing.vue:1188_
   
   ➝ This confirms the issue is UI-related, not API-related.
   
   <img width="2047" height="294" alt="image" 
src="https://github.com/user-attachments/assets/7e304403-fb2b-4266-b422-343c925f0c23";
 />
   
   Backend log showing malformed CIDR string (space between 1st and 2nd CIDR) 
received during UpdateLoadBalancerRuleCmd.
   
   [Screencast from 2025-10-09 
15-02-15.webm](https://github.com/user-attachments/assets/a9594ed1-e09d-4ee1-a5ac-ee579c1fcbe5)
   
   **Summary**:
   
   - Multiple CIDRs work on rule creation.
   - Single CIDRs work on rule creation.
   - Multiple CIDRs break when editing due to the UI transforming the CIDR list 
incorrectly.
   - API itself accepts the correct format.
   
   Happy to retest after a fix.


-- 
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