You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As already stated in ansible/ansible#38605 the networks field in the vmware_guest module is not idempotent. Ansible always reports a change even when the virtual machine is already in the target state.
After some investigations I have found out that the portgroup_portkey toogles in every run. In my case the value changes between 1348 and 1350. The next run gives:
SUMMARY
As already stated in ansible/ansible#38605 the
networks
field in thevmware_guest
module is not idempotent. Ansible always reports a change even when the virtual machine is already in the target state.ISSUE TYPE
COMPONENT NAME
vmware_guest
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
None.
OS / ENVIRONMENT
vSphere 7.0.3
STEPS TO REPRODUCE
Create a virtual machine, that uses the
networks
fields:Let Ansible create the virtual machine and re-execute the play without any modifications.
EXPECTED RESULTS
Ansible should not report any changes for this virtual machine.
ACTUAL RESULTS
Ansible reports a change very time when the play is executed.
After some investigations I have found out that the
portgroup_portkey
toogles in every run. In my case the value changes between1348
and1350
. The next run gives:To summarize the change:
As already stated in this post ansible/ansible#38605 (comment) the issue is caused by this code fragment in
vmware_guest.py
(line 1826-1828):The comparison does not succeed because the two values are not equal:
Any ideas, how we can solve the issue?
The text was updated successfully, but these errors were encountered: