-
Notifications
You must be signed in to change notification settings - Fork 338
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
Fix vmware_guest idempotency when using dvswitch (fixes #498) #2000
base: main
Are you sure you want to change the base?
Fix vmware_guest idempotency when using dvswitch (fixes #498) #2000
Conversation
b4f47f8
to
7fc61f6
Compare
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 9m 40s |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 10m 19s |
92da7f8
to
b385e03
Compare
@mariolenz Would it be possible to get this merged? Thanks! |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 8m 14s |
Sorry, I've overlooked this PR for far too long. I think we had some changes to the module. Could you please re-base your fork just to make sure there are no merge conflicts? |
b385e03
to
9dd08fe
Compare
@mariolenz Done. |
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 4m 36s |
SUMMARY
This fixes the idempotency issue reported in #498 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