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
In scenario where portgroup with same name is present on both vSwitch and dvSwitch and network is configured by using pyvmomi, it is always assigned to vSwitch, even despite the fact that ESXi host in question only that specific portgroup available only on dvSwitch
Reproduction steps
Create VM with dvSwitch portgroup TEST1 on ESXi host with dvSwitch
Change VM portgroup to TEST2 with pyvmomi (portgroup with this name should be available on vSwitch and dvSwitch on same or any other host)
...
Expected behavior
I expect portgroup to be assigned from the portgroups that are available on the ESXi host where VM is running on
Describe the bug
In scenario where portgroup with same name is present on both vSwitch and dvSwitch and network is configured by using
pyvmomi
, it is always assigned to vSwitch, even despite the fact that ESXi host in question only that specific portgroup available only on dvSwitchReproduction steps
pyvmomi
(portgroup with this name should be available on vSwitch and dvSwitch on same or any other host)...
Expected behavior
I expect portgroup to be assigned from the portgroups that are available on the ESXi host where VM is running on
Additional context
Network was changed by running this python script by running command:
The text was updated successfully, but these errors were encountered: