I have found a way to mitigate this, but I don't like it.
I am migrating from an old 5.1 ESXi cluster to a new VXrail. I used one of the 5.1 ESXi hosts as a swing host of sorts. Make sure the VMs I am migrating are on the swing host, disconnect it from the vcenter and connect it to the VXrail.. then I do a host/storage migration to the VXrail. So that all works, I''m about half way through 500 VMs - then I notice that if the swing host isn't connected to the VXRail data center, I can't power on VMs that have been migrated. It says can't power on the VM in the host current state and lists the swing host. Have double checked everything and there is nothing depending on that host. Have migrated the VM to another host in the VXrail and same problem.
I can start the vim from the ESXi shell on the host itself using vim-cmd, however the problem persists in the vsphere client... both the thick and the web client have this problem.
The one work around I have found is to delete the VM from inventory and then re-add it, but not looking forward to doing that with nearly 500 vms!
Anyone else seen this and have any better solution? I have tried restarting services on the hosts and no change either.
The VXrail is running 6U2 I believe and the old vcenter is 5.1.
Thanks
Bill