[Bug]: Contact Assignment Module modifies existing contact_assignment

[janhoelscher]

Ansible NetBox Collection version

devel

Ansible version

ansible [core 2.17.6]
  config file = /Users/<hidden>/git/test/netbox-forms/ansible.cfg
  configured module search path = ['/Users/<hidden>/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/homebrew/lib/python3.13/site-packages/ansible
  ansible collection location = /Users/<hidden>/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/homebrew/bin/ansible
  python version = 3.13.5 (main, Jun 11 2025, 15:36:57) [Clang 17.0.0 (clang-1700.0.13.3)] (/opt/homebrew/opt/python@3.13/bin/python3.13)
  jinja version = 3.1.4
  libyaml = True

NetBox version

v4.4.2

Python version

3.11

Steps to Reproduce

1. Create a random contact assignment with a specific role for, in my case, a vm with name
2. Execute the contact_assignment module to add a contact assignment for the same role but another person

Playbook looks like this:

   - name: "Assign Serveradmins to Contactassignments"
      netbox.netbox.netbox_contact_assignment:
        netbox_url: "{{ nb_host }}"
        netbox_token: "{{ nb_token }}"
        data:
          object_type: virtual_machine
          object_name: "<vm-name>"
          contact: "<name-new-contact>"
          role: "Serveradmin"
        state: present

Expected Behavior

The new created contact assignment should exits, while the other should also exists

Observed Behavior

The first created contact assignment will be overwritten.
So only one exists.

Output looks like this:

changed: [localhost] => {
    "changed": true,
    "contact_assignment": {
        "contact": 513,
        "created": "2025-11-05T13:40:46.755563Z",
        "custom_fields": {},
        "display": "<name-old-contact> -> <vm-name>",
        "id": 1669,
        "last_updated": "2025-11-05T13:40:46.755578Z",
        "object": 903,
        "object_id": 903,
        "object_type": "virtualization.virtualmachine",
        "priority": null,
        "role": 2,
        "tags": [],
        "url": "<netbox-host>/api/tenancy/contact-assignments/1669/"
    },
    "diff": {
        "after": {
            "contact": 513
        },
        "before": {
            "contact": 468
        }
    },
    "invocation": {
        "module_args": {
            "cert": null,
            "data": {
                "contact": "<name-new-contact>",
                "object_name": "<vm-name>",
                "object_type": "virtual_machine",
                "priority": null,
                "role": "Serveradmin",
                "tags": null
            },
            "headers": null,
            "netbox_token": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
            "netbox_url": "<netbox-host>",
            "query_params": null,
            "state": "present",
            "validate_certs": true
        }
    },
    "msg": "contact_assignment <name-new-contact> -> <vm-name> updated"
}

[sc68cal]

If you want multiple contacts to be associated, you need to provide both contacts (if that is supported by NetBox) in the task. I do not believe this is a bug.

[janhoelscher]

I have tried to use a list of contacts, which is currently not supported.

I think the solution would be a correct use of query_params. This would specify the "scope" of the request and what makes a object, in this case a contact assignment unique.

I have observed this in virtual machine module, if you first create a vm on cluster-a and you want to move to cluster-b you have to specify that the virtual machine name is the query_param, because otherwise you create a new vm with the same name on cluster-b.

[janhoelscher]

Also i have observed some other "bug" which is maybe related.

If i am having two contacts with the same role, in my case "Serveradmin" and try to remove one via state: absent the module return "More than one result returned for -> "