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 I try to add binding members to an existing service group in desired mode, it's giving me a 409 error and won't let the additional members get added; however, I can remove members from an existing service group in the same way when altering my variable value.
To add some clarity to this, I can add as many brand new binding members as I want during an initial run, but once they exist, I can only remove or stay with the same number; trying to add more results in the above conflict error.
Sure, using the Ansible that's in the "Steps to Reproduce" section, I:
Create the new service group with two (or more) server IPs for the binding per the netscaler_serverip variable's value (e.g. "172.20.1.1, 172.20.1.2").
Initial creation succeeds with both binding members present, and then I attempt to add an additional IP via the variable value (e.g. "172.20.1.1, 172.20.1.2, 172.20.1.3"), and it will fail with the 409 error above (even though the additional IP ["172.20.1.3"] does not exist in the binding).
If I take out an IP from the original variable value (e.g. "172.20.1.1"), it will gladly remove the binding member that was taken out (e.g. "172.20.1.2").
Rinse and repeat on any additional new service groups.
Summary
When I try to add binding members to an existing service group in desired mode, it's giving me a 409 error and won't let the additional members get added; however, I can remove members from an existing service group in the same way when altering my variable value.
Issue Type
Bug Report
Component Name
servicegroup module; servicegroup_servicegroupmember_binding section
Python Version
Ansible Version
Ansible Configuration
netscaler.adc Collection Version
Target NetScaler Version
Equivalent NetScaler CLI Command
Steps to Reproduce
Expected Results
I would expect it to add the additional member IPs rather than error out about a conflict of existence.
Actual Results
Additioinal Notes
There's a typo in "Additional" in this section header, FYI.
The text was updated successfully, but these errors were encountered: