-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stable-4.x: Fix vmware_guest idempotency whith dvswitch #2254
stable-4.x: Fix vmware_guest idempotency whith dvswitch #2254
Conversation
Build failed. ✔️ ansible-tox-linters SUCCESS in 4m 28s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 4m 24s |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 4m 42s |
@Yannik FYI I'm not sure why the CI fails. Maybe it's only a temporary issue. I'll try again tomorrow, but if it still fails I'll have to troubleshoot the CI a bit :-/ |
recheck |
Build failed. ✔️ ansible-tox-linters SUCCESS in 4m 39s |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 4m 41s |
Build succeeded (gate pipeline). ✔️ ansible-tox-linters SUCCESS in 5m 06s |
5877a03
into
ansible-collections:stable-4.x
SUMMARY
This fixes the idempotency issue caused by
nic.device.deviceInfo.summary
containingDVSwitch: d5 6e 22 50 dd f2 94 7b-a6 1f b2 c2 e6 aa 0f
instead of a readable portgroup name.ISSUE TYPE
COMPONENT NAME
vmware_guest
ADDITIONAL INFORMATION
Backport of #2000
#498