vSphere Provider: Fix #8253

[cvlc]

Body:
If we only have one networkInterface, deviceID should be 0 to ensure that it selects the first element of the networkInterfaces array.

I don't have a development vSphere environment handy for running tests and have only used it with one configuration, hence the WIP.

[astraios]

Hi,

Is there any way we could have this merged, I'm still experimenting this issue with 0.7.3.

Thanks

[justinclayton]

This works for us in our vCenter 6 environment. LGTM!

[justinclayton]

Yo, this has been well tested at this point and is a very minor change to fix an otherwise crashing bug. We've been working off a fork for a while now; any chance this can make it into 0.7.7?

[jgeerds]

This patch works for us as well. What blocks this PR from being merged?

[cvlc]

Maybe we need @stack72 or somebody else with write access?

[RicharddeJong]

My Terraform is now also crashing on the same point. Can someone add this to the main branch please?

[stack72]

Hi friends,

Sorry that we haven't merged this in. We are currently in the process of setting up some acceptance testing infrastructure for vsphere. If someone already has ran the acceptance tests with this patch, please can they post the results here?

This will help us immensely!

Thanks

Paul

[jgeerds]

@stack72: Do the tests have "unexpected" side effects? (e.g. remove all VMs from the cluster or not properly clean up?)

[curator]

@stack72 With some fumbling about, my team was able to setup a testing environment and the acceptance tests for networking ran clean with the patches.

[krobertson]

This is also working on my local vSphere 6 cluster. Would be great to have it merge and be in the next release.

[curator]

@stack72 Do you need anything else before merging this?

[matt-deboer]

Any chance this could be merged soon?
Already using it, but hate maintaining a fork...

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.