Details
Description
When creating a VR, CS tries creates the public VLAN on the vSwitch0 even if we told him to use vSwitch2 during the Zone setup.
Expected behaviour is that CS creates the port-group only where it should be, so on vSwitch2 in our case. See the snapshot included.
From the log:
Preparing NIC device on network cloud.public.142.0.1-vSwitch0
INFO [vmware.resource.VmwareResource] (DirectAgent-47:yul01vi13.ops.dot) Prepare NIC device based on NicTO:
INFO [vmware.resource.VmwareResource] (DirectAgent-47:yul01vi13.ops.dot) Prepare network on vSwitch: P[vSwitch0:untagged] with name prefix: cloud.public
INFO [vmware.mo.HypervisorHostHelper] (DirectAgent-47:yul01vi13.ops.dot) Network cloud.public.142.0.1-vSwitch0 is ready on vSwitch vSwitch0
INFO [vmware.mo.HypervisorHostHelper] (DirectAgent-47:yul01vi13.ops.dot) Network cloud.public.142.0.1-vSwitch0 is ready on vSwitch vSwitch0
INFO [vmware.resource.VmwareResource] (DirectAgent-47:yul01vi13.ops.dot) Preparing NIC device on network cloud.public.142.0.1-vSwitch0