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
netscaler.adc.sslprofile_sslcipher_binding does not work as expected.
Binding ciphers to sslprofile for 2nd time throws an error:
{'errorcode': 3741, 'message': 'Specified cipher is already bound with higher priority', 'severity': 'ERROR'}
Unbinding "DEFAULT" ciphers group does not work either.
Describe the bug
netscaler.adc.sslprofile_sslcipher_binding does not work as expected.
Binding ciphers to sslprofile for 2nd time throws an error:
{'errorcode': 3741, 'message': 'Specified cipher is already bound with higher priority', 'severity': 'ERROR'}
Unbinding "DEFAULT" ciphers group does not work either.
SSL default profile is enabled on VPX.
To Reproduce
Steps to reproduce the behaviour:
I am seeing the below error...
{'errorcode': 3741, 'message': 'Specified cipher is already bound with higher priority', 'severity': 'ERROR'}
Expected behaviour
Environment (please complete the following information):
ansible-galaxy collection list | grep netscaler.adc
netscaler.adc 2.0.1
Python version
python --version
Python 3.6.8
Ansible version
ansible --version
ansible [core 2.11.12]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/xxx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/xxx/projects/.venv/lib/python3.6/site-packages/ansible
ansible collection location = /home/xxx/.ansible/collections:/usr/share/ansible/collections
executable location = /home/xxx/projects/.venv/bin/ansible
python version = 3.6.8 (default, May 30 2023, 08:41:09) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]
jinja version = 3.0.3
libyaml = True
NetScaler version
show ns version
outputNetScaler NS13.0: Build 87.9.nc, Date: Jul 29 2022, 10:59:37 (64-bit)
PS also tested on 13.1 latest 49.13
Additional context
Have also tried using netscaler.adc.sslprofile with desired mode - but that did not work either
The text was updated successfully, but these errors were encountered: