VIC Management portal does not update container from error status
search cancel

VIC Management portal does not update container from error status


Article ID: 340335


Updated On:


VMware vSphere ESXi


If there is a network connection loss between the VCH endpoint VM and the VIC appliance VM, Management portal does not change container status from error to running state.


VMware vSphere Integrated Containers 1.0.x


This issue occurs due to multiple issue with the early version of the health checker in early versions of admiral.


To resolve the issue in the admiral health checker, upgrade to VIC 1.2, available at VMware Downloads.
If the issue persists after upgrading, validate that the network connection between the following is not failing.

  • VCH endpoint VM
  • vCenter Server
  • VIC Appliance VM

More information can be seen in the admiral logs to troubleshoot further. The admiral.service logs are located on the VIC appliance VM and are access with the following command journalctl -u admiral.service from the shell.

To access the shell:

  1. Shut down the vSphere Integrated Containers appliance by selecting Shut Down Guest OS.
Note: Do not select Power Off.
  1. Right-click the new vSphere Integrated Containers appliance, and select Edit Settings.
  2. Click vApp Options to modify the settings that you provided when you used the OVA installer to deploy the appliance.
  3. In Appliance Security, update the password for the appliance root account, enable or disable SSH log in.
  4. Click OK to close the Edit Settings window.
  5. Power on the vSphere Integrated Containers appliance.
  6. Use preferred SSH client to connect under the user root.

If upgrade to VIC 1.2 does not correct the issue, see Troubleshooting vSphere Integrated Containers.