Deployment of Containers VM fails after changing vCenter network infrastructure

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:
You see a message similar to the following while attempting to deploy Containers-VM from the docker client:

docker: Error response from daemon: Server error from portlayer: [POST /scopes/{scope}/containers][500] addContainerInternalServerError &{Code:0 Message:ServerFaultCode: The object 'vim.dvs.DistributedVirtualPortgroup:dvportgroup-xxxxxx' has already been deleted or has not been completely created}.

Environment

VMware vSphere Integrated Containers 1.x

Resolution

This issue can occur when VCH uses a vDS port group for the public network that has been removed in vCenter. To resolve this issue, redeploy VCH using a new port group.

1. Redeploy a new VCH using a new vDS port group
2. Gracefully shutdown the Container VMs on the old VCH
3. Start Container VMs on the new VCH pointing to the same volumes that were in use on the old VCH. 

Note: It is required to have Volumes configured for the Containers-VM to implement this resolution.