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
We could choose to ignore changes to managedFields. But changes to annotations could be an issue. However, I see that you did not specify annotations in your call to kubevirt.core.kubevirt_vm, so indeed, it should not care about those.
This issue with managedFields happens with other resources as well, so I think this one should be resolved with k8s module. But the kubemacpool.io/transaction-timestamp I think come from some pre-hook which inject the MAC if it's not in the request.
I was not able to reproduce it on the KubeVirt cluster provided by hack/e2e-setup.sh. I noticed though that your are using 3.2.0 of kubernetes.core. Can you try again with version 5.0.0 of kubernetes.core?
SUMMARY
Running the same task with the same input, show the VM changed. While nothing significant was change only some timestamps.
ISSUE TYPE
ANSIBLE VERSION
COLLECTION VERSION
STEPS TO REPRODUCE
From the examples
EXPECTED RESULTS
First run should create the VM (if the vm dose not exist)
Second run should report nothing change for the same input.
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: