• From the CLI, running the vic-machine ls command does not list VCH VM in the output:
  
  ./vic-machine ls --target vcsa.vsphere.local --user [email protected] --thumbprint F6:B4:06:A4:B5:01:5E:31:66:18:E2:E4:3B:B5:6F:28:51:20:E3:3B
  
  Aug 17 2017 08:14:56.820Z INFO vSphere password for [email protected]:
  Aug 17 2017 08:15:00.856Z INFO ### Listing VCHs ####
  Aug 17 2017 08:15:01.158Z INFO Validating target
  
  ID PATH NAME VERSION UPGRADE STATUS
  
• From the CLI, running the vic-machine debug command does not recognize VCH as a VCH:
  
  ./vic-machine debug --target vcsa.vsphere.local --user [email protected] --thumbprint F6:B4:06:A4:B5:01:5E:31:66:18:E2:E4:3B:B5:6F:28:51:20:E3:3B --compute-resource Compute-01 --name vch-01
  
  Aug 17 2017 08:17:09.460Z INFO vSphere password for [email protected]:
  Aug 17 2017 08:17:13.737Z INFO ### Configuring VCH for debug ####
  Aug 17 2017 08:17:13.959Z INFO Validating target
  Aug 17 2017 08:17:14.053Z ERROR Not a VCH
  Aug 17 2017 08:17:14.053Z ERROR Failed to get Virtual Container Host vch-01
  Aug 17 2017 08:17:14.053Z ERROR Not a VCH
  Aug 17 2017 08:17:14.053Z ERROR --------------------
  Aug 17 2017 08:17:14.053Z ERROR vic-machine debug failed: debug failed
  
• The docker daemon is not running when you try to execute a docker command:
  
  docker -H vch-01.vsphere.local:2376 --tls info
  Cannot connect to the Docker daemon at tcp://vch-01.vsphere.local:2376. Is the docker daemon running?
  
• The VM's /vmfs/volumes/datastore/virtual machine/vwmare.log file reports an issue with docker-personality:
  
  2017-08-17T08:04:10.690Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.detail.stoptime = <not printed>
  2017-08-17T08:04:10.704Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.status = <not printed>
  2017-08-17T08:04:13.867Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.diagnostics.resurrections = <not printed>
  2017-08-17T08:04:17.052Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.detail.stoptime = <not printed>
  2017-08-17T08:04:20.243Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.diagnostics.resurrections = <not printed>
  2017-08-17T08:04:23.373Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.detail.stoptime = <not printed>
  2017-08-17T08:04:26.535Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.diagnostics.resurrections = <not printed>
  2017-08-17T08:04:29.648Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.detail.stoptime = <not printed>
  2017-08-17T08:04:32.817Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.diagnostics.resurrections = <not printed>
  2017-08-17T08:04:36.413Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.detail.stoptime = <not printed>
  2017-08-17T08:04:39.588Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.diagnostics.resurrections = <not printed>
  2017-08-17T08:04:42.839Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.detail.stoptime = <not printed>
  2017-08-17T08:04:45.997Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.diagnostics.resurrections = <not printed>
  2017-08-17T08:04:49.204Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.detail.stoptime = <not printed>
  2017-08-17T08:04:52.385Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.diagnostics.resurrections = <not printed>
  2017-08-17T08:04:55.604Z| vcpu-0| A100: ConfigDB: Setting guestinfo.vice..init.sessions|docker-personality.detail.stoptime = <not printed>

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

This issue occurs because VCH VM was deleted from the vCenter inventory and then added back to the vCenter inventory changing the VCH VM's vm-id (MOID). Due to this change, the VIC services are no longer using the correct vm-id (MOID).

1. Re-register the VCH to the initial vApp.
   
2. Get the new vm-id from the MOB:
   
   
   1. Browse to the MOB and login to https://vcsa.vsphere.local/mob.
   2. Click content > rootFolder property.
   3. In the childEntity property, click on the datacenter were your VCH is running.
   4. In the datastore property, click on the datastore where is VCH is stored.
   5. Find the vm-id of the VCH in the vm property.
3. Power off the VCH.
4. Edit the VMX file of the impacted VCH and search for the line starting with guestinfo.vice./init/common/id.
5. Update the value of guestinfo.vice./init/common/id with the new vm-id found in the MOB.
6. Power on the VCH.