Validation error when adding a new cable

[napaster]

NetBox version

v3.4.6

Python version

3.10

Steps to Reproduce

ansible-playbook tasks/netbox/6_conneted.yml

6_conneted.yml

---
- name: Cable
  become: false
  gather_facts: false
  remote_user: napaster
  no_log: false
  strategy: linear
  serial: 1
  connection: local
  hosts: localhost
  tasks:
    - name: Create cable within NetBox with only required information U1
      netbox.netbox.netbox_cable:
        netbox_url: "{{ netbox_api_endpoint }}"
        netbox_token: "{{ netbox_api_token }}"
        data:
          termination_a_type: dcim.interface
          termination_a:
            device: omsk.opentech.local
            name: gig0
          termination_b_type: dcim.interface
          termination_b:
            device: omsk-krput79-st1.opentech.local-u1
            name: GigabitEthernet1/0/24
        state: present

After that I run the playbook and get:
"msg": "{"all":["Must define A and B terminations when creating a new cable."]}"

1. Create device omsk.opentech.local
2. Create an interface on the device named gig0
3. Create device omsk-krput79-st1.opentech.local-u1.
4. Create an interface on the omsk-krput79-st1.opentech.local-u1 device with the name GigabitEthernet1/0/24 type 1000base-t

Next, I tried to create a cable with a playbook. The manual cable is created.

Expected Behavior

Cable created successfully

Observed Behavior

"msg": "{"all":["Must define A and B terminations when creating a new cable."]}"

[candlerb]

There was a major change in the cable data model and REST API in Netbox version 3.3: cables now have multiple terminations at each end, rather than a single termination.

Therefore, code you wrote (or found) which worked on versions prior to 3.3 won't work on 3.3 onwards.

In general, there's no guarantee that X.Y and X.Y+1 are compatible with each other: so every time you upgrade, you may have to update your integrations, scripts, reports etc. These changes are called out in the release notes.

[napaster]

OK. Clearly, it is possible then a proverb on the documentation how to start parvilno? Well, or just a request for it? Don't study inside and out.
I took a description similar to https://docs.ansible.com/ansible/latest/collections/netbox/netbox/index.html

[candlerb]

You mean at https://docs.ansible.com/ansible/latest/collections/netbox/netbox/netbox_cable_module.html#ansible-collections-netbox-netbox-netbox-cable-module ?

Yeah, that looks out of date to me.

I think the source is here: https://github.com/netbox-community/ansible_modules/blob/devel/docs/plugins/netbox_cable_module.rst - you can raise an issue in that repo to get the examples updated.

However, I believe that the structure of these requests is the same as that used by the REST API. So if you follow the link I gave you to the version 3.3 release notes, you can see the changes - e.g. termination_a has been replaced by a_terminations which is a list [...]

Sorry, I can't give you a ready-to-run example for Ansible, but you can get some clues by hitting the REST API of a live Netbox instance:

$ curl -fsS -H "Authorization: Token 1111111111111111111111111111111111111111" https://demo.netbox.dev/api/dcim/cables/1/ | python3 -mjson.tool
{
    "id": 1,
    "url": "https://demo.netbox.dev/api/dcim/cables/1/",
    "display": "#1",
    "type": "smf",
    "a_terminations": [
        {
            "object_type": "circuits.circuittermination",
            "object_id": 15,
            "object": {
                "id": 15,
                "url": "https://demo.netbox.dev/api/circuits/circuit-terminations/15/",
                "display": "DEOW4921: Termination Z",
                "circuit": {
                    "id": 14,
                    "url": "https://demo.netbox.dev/api/circuits/circuits/14/",
                    "display": "DEOW4921",
                    "cid": "DEOW4921"
                },
                "term_side": "Z",
                "cable": 1,
                "_occupied": true
            }
        }
    ],
    "b_terminations": [
        {
            "object_type": "dcim.interface",
            "object_id": 157,
            "object": {
                "id": 157,
                "url": "https://demo.netbox.dev/api/dcim/interfaces/157/",
                "display": "GigabitEthernet0/0/0",
                "device": {
                    "id": 13,
                    "url": "https://demo.netbox.dev/api/dcim/devices/13/",
                    "display": "dmi01-yonkers-rtr01",
                    "name": "dmi01-yonkers-rtr01"
                },
                "name": "GigabitEthernet0/0/0",
                "cable": 1,
                "_occupied": true
            }
        }
    ],
    "status": {
        "value": "connected",
        "label": "Connected"
    },
    "tenant": null,
    "label": "",
    "color": "ffeb3b",
    "length": null,
    "length_unit": null,
    "description": "",
    "comments": "",
    "tags": [],
    "custom_fields": {},
    "created": "2020-12-30T00:00:00Z",
    "last_updated": "2020-12-30T19:32:32.279000Z"
}

[napaster]

Yes, that's the mod I meant. I just clicked the link where I see the syntax for writing playbooks. Apparently in one place it has changed in another not. I will write with a request to correct the documentation. Now it has become more clear. Thank you