To workaround the issue, please follow anyone of the two procedures mentioned below:
Option 1 : Reload the Virtual Machine and then connect vnic manually.
OR
Option 2: onnect Virtual Machine's vnic to other pg/dvpg/LS, then change it back to original LS, and then connect vnic manually.
You can download the script attached to the KB to automatically remediate using Option 2.