Hello,
Thank you for taking the time to read this thread. Our team is experiencing an issue where the network adapter in vCenter gets assigned incorrectly when provisioning a VM from vRA. Let me first explain the configuration, then I'll explain the behavior in depth.
We have a business group that is has only one reservation associated with it. That reservation is shown here:
As you can see there are two network profiles, which are only configured to use the network adapters that are associated with them in the reservation. Meaning, if the wrong adapter is assigned to the network, as you would expect, it won't be able to communicate.
From the vRA Blueprint side, have a custom property VirtualMachine.Network0.ProfileName that is displayed as a dropdown on the Blueprint. This is shown below with the values:
It's my understanding that if we assign the network profile, by name to this property is should provision an IP out of that range (which it does) and set the network adapter accordingly. The issue we are experiencing is that the VM receives and IP in the correct network range 100% of the time, but the network adapter almost randomly gets assigned between the adapters that are configured in the reservation. Meaning, in this case either the adapter ending TEST1_epg or TEST4_epg (shown above).
I have confirmed also that the we do have a vm customization spec defined. I had an issue with this previously and was able to fix with help from this community. (Thanks again!)
Please let me know if there is any additional information needed to help troubleshoot this issue. Our team is kind of at a loss regarding this behavior.