Open allan-silverstein opened 1 year ago
Verify that your ansible collection and netbox server versions match, since it is failing because the console-server-ports
API endpoint is not being exposed by the NetBox server that you are connecting to.
Sorry about the delayed response.... Not sure about the correlation between ansible collection version and the Netbox server version but here is what I have: Netbox Server: 3.5.2 Ansible Galaxy netbox collection: 3.13.0
They obviously don't match but I believe that is the latest of each or pretty close to it. Are these the versions you were referring to or something else?
# /home/asilver/.ansible/collections/ansible_collections
Collection Version
------------------ -------
ansible.netcommon 4.0.0
ansible.posix 1.4.0
ansible.utils 2.6.1
community.general 5.8.0
community.vmware 3.1.0
dellemc.openmanage 6.3.0
dellemc.os10 1.1.1
dellemc.powerscale 1.9.0
dellemc.powerstore 1.7.0
netbox.netbox 3.13.0
Related to - https://github.com/netbox-community/ansible_modules/issues/1040
I also have the exact same issue when using dcim.frontports.
dcim.interfaces however do work okay.
Ansible NetBox Collection version
v3.13.0
Ansible version
NetBox version
v3.5.2
Python version
3.10
Steps to Reproduce
Running this simple playbook the first time works fine and the cable connection between dcim.consoleserverport and dcim.consoleport is created. Running subsequent times results in errors. This seems to be related to https://github.com/netbox-community/ansible_modules/issues/989
Expected Behavior
Idempotency should work where the same playbook can be run multiple times without adding the cable if the cable all ready exists.
Observed Behavior
Here is what happens when running it. Note, there are warning cert errors in module_stderr that show up which are not related to the issue. The error is at the end of module_stderr:
Exception: console-server-ports not found in API_APPS_ENDPOINTS\n",