-
Notifications
You must be signed in to change notification settings - Fork 54
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
[Bug]: service does not accept custom monitor - 'Default monitor cannot be unbound from a service' #312
Comments
@pkodzis, thank you for the issue. Before I give a fix, please try the below workaround.
![]() |
Yes, it functions with "bind" mode. However, this isn't a workaround that I can integrate into our pipeline to replace the existing 1.3.0 Citrix ADC collection. Our pipeline delegates all the monitor binding logic to Ansible and 1.3.0 collection does it for us just fine. Using "bind" mode with 2.0.3 would necessitate a redevelopment of the pipeline to check the state and then create the expected unbind/bind statements. |
… cannot be unbound from a service' Signed-off-by: Sumanth Lingappa <sumanth.lingappa@cloud.com>
This issue is fixed in the latest release |
ack - it's resolved in 2.1.0. thank you so much! :) |
Summary
I'm unable to bind custom monitor to the service. Errors says it is impossible to do not use default monitor.......
"msg": "ERROR: delete_resource FAILED; status_code: 599; Reason:{'errorcode': 2164, 'message': 'Default monitor cannot be unbound from a service', 'severity': 'ERROR'}"
Issue Type
Bug Report
Component Name
service
Python Version
Ansible Version
Ansible Configuration
$ ansible-config dump --only-changed
netscaler.adc Collection Version
Target NetScaler Version
Equivalent NetScaler CLI Command
Steps to Reproduce
Expected Results
service using custom monitor instead of default one
Actual Results
Additioinal Notes
No response
The text was updated successfully, but these errors were encountered: