During a migration process, we were annoyed by a wrong datastore appearing in the virtual machines summary. It was the old ISO datastore that was no longer accessible and no longer configured on the ESXi hosts.
The first thing to do was to manually remove any ISO files configured on the virtual machines, but the problem remains the same for some and was solved for others.
During our the tests I’ve noticed that if the virtual machine has a snapshot and if this snapshot was taken during a phase where the ISO file was mounted, the stuck/inactive datastore appears.
To solve the problem, remove the ISO files from the settings and then remove all snapshots that was taken before the migration.
I’m not sure, but the same problem related to the network interfaces can be solved with the same method…