-
Notifications
You must be signed in to change notification settings - Fork 254
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Ansible NetBox Collection version
v3.19.1
Ansible version
ansible --version
ansible [core 2.17.7]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.10/dist-packages/ansible
ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible
python version = 3.10.12 (main, Aug 15 2025, 14:32:43) [GCC 11.4.0] (/usr/bin/python3)
jinja version = 3.1.6
libyaml = TrueNetBox version
v4.4.2
Python version
3.10
Steps to Reproduce
You can define a Virtual Machine linked to a specific cluster, when you want to update VM cluster, ansible try to create a new virtual machine object. There is no way to update a VM cluster without deleting the VM and recreating it.
Expected Behavior
Ansible should update VM cluster instaed of recreating a new VM or there would have a way to specify if we would like to update the cluster or create a new VM.
Observed Behavior
A new VM is created with that new cluster and the other VM is not update.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working