[Bug]: server Module Not Idempotent with New Collection 2.7.0 (Works in 2.6.1)

[cepitacio]

Summary

The netscaler.adc.server module works as expected (idempotent) in version 2.6.1. However, in version 2.7.0, running the same task multiple times results in unintended changes, breaking the idempotent behavior.

Issue Type

Bug Report

Component Name

server

Python Version

python version 3.11.0

Ansible Version

2.14.5

Ansible Configuration

- name: add server
  netscaler.adc.server:
    nsip: redacted
    nitro_protocol: redacted
    nitro_user:  redacted
    nitro_pass: redacted
    validate_certs: redacated
    state: present
    name: 192.168.1.10
    ipaddress: 192.168.1.10

netscaler.adc Collection Version

2.7.0

Target NetScaler Version

> show ns version

Equivalent NetScaler CLI Command

Steps to Reproduce

Run the playbook with version 2.6.1 and confirm that no changes are made if the resource already exists (idempotent behavior).
Upgrade to version 2.7.0.
Re-run the same playbook, and observe that the task results in "Resource already exists" and the server is unnecessarily recreated or modified.

Expected Results

The module should be idempotent, with no changes unless the resource needs to be updated or created.

Actual Results

The module fails and returns "Resource already exists" if resource was already created.

Additional Notes

No response