vMotion fails for a specific host with message “The Object or item referred to could not be found”

I was working with one of VMware account last week for some vSAN issues. I fixed multiple issues related to vSAN and closed the request.

Suddenly customer raised a concern that he is unable to move the virtual machines for a specific host which had issues earlier. I checked the host it is a part of vSAN cluster but none of the vSAN issues were found.

I tried few steps as per below:

1.) Migrated the existing machine to reproduce the issue and it failed with same error.

2.) Created a new virtual machine on impacted host and tried to migrate. The migration completed successfully.

3.) Chose existing non-critical virtual machine, unregistered and re-registered the VM. Initiated migration and completed successfully.

After checking above steps, I suspect there are some issues with this host only not virtual machines.

I went ahead and checked hostd.log file on the host and below errors were found:

/var/log/hostd.log :

 error hostd[2233] [Originator@3434sub=Hostsvc.NsxSpecTracker] Object not found/hostspec disabled
 error hostd[2233] [Originator@3434sub=Hostsvc.NsxSpecTracker] Object not found/hostspec disabled
 info hostd[2233] [Originator@3434sub=Solo.Vmomi opID=888888-7f00 user=vpxuser] Result:
–> (vim.fault.PlatformConfigFault) {
–> faultCause = (vmodl.MethodFault) null,
–> faultMessage = (vmodl.LocalizableMessage) [
–> (vmodl.LocalizableMessage) {
–> key = “com.vmware.esx.hostctl.default”,
–> arg = (vmodl.KeyAnyValue) [
–> (vmodl.KeyAnyValue) {
–> key = “reason”,
–> value = “Unable to delete DVPort “” that is in use, use list: EVM.eth0″
–> }
–> ],
–> message = <unset>
–> }
–> ],
–> text = “”
–> msg = “”
–> }

After checking this error “Unable to delete DVPort “” that is in use” my approach moved to vDS. I chose another non-critical virtual machine and checked the port group it is mapped to. It seemed that VM is mapped to correct port group and VLAN, connectivity is also fine but it is not showing any connection to uplinks.

In order to reassign the port group ID, I followed the below procedure.

  • Right click on the vDS and choose Add and Manage Hosts
  • Select Manage host networking

  • Click on + icon and select the impacted host

  • Uncheck all the options and check migrate virtual machine networking

  • Select the virtual machine which you want to assign port id
  • Click on assign port group and choose the same port group as source for destination PG

 

  • Now to check source PG and Destination PG are same

  • Click Finish and task will be completed successfully

Now, try to migrate a virtual machine it will be completed successfully.

You can apply the same workaround on all the impacted virtual machines and issue will be resolved.

This actually happens in the instances where we re-add the existing host into DVS ( After removing it from DVS for some purposes) and we do not migrate the VM networking correctly. Hence, it will cause issues related to DVS port ID.

 

I hope this article is useful for you guys.

 

Enjoy learning!!

Be the first to comment

Leave a Reply

Your email address will not be published.


*