Possible Inventory Issues Observed After Host Rollback
search cancel

Possible Inventory Issues Observed After Host Rollback

book

Article ID: 410936

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

After performing a rollback, the following issues may be observed in the vSphere Client inventory on the rolled-back host.

Note: These are inventory display issues only. They do not affect the actual running virtual machines.

  • Virtual machines that were migrated onto the host after the upgrade/update but before the rollback:
    These appear as “orphaned” in the vSphere Client inventory.

  • Virtual machines migrated from the rollback target host to another host may appear on the rolled-back host with a VMX file path and be shown as "inaccessible".

Environment

VMware vSphere ESXi

Resolution

Follow these steps:

  1. For virtual machines displayed as “inaccessible” or “orphaned”, perform “Remove from Inventory” in the vSphere Client.

  2. Re-register the virtual machines that were originally registered on the rollback target host.

Additional Information

This issue does not occur if no virtual machine migrations take place between the upgrade and the rollback.
Therefore, it is recommended to migrate virtual machines before the upgrade to prevent this situation.

Virtual machines appear as invalid or orphaned or inaccessible