vSAN Virtual Objects reporting Unknown object state of objects that are hosted in another vSAN cluster
Article ID: 326655
Updated On:
Products
VMware vSAN
Issue/Introduction
Symptoms:
- vCenter managing multiple vSAN clusters.
- vCenter upgrade to 7.0U3c or higher.
- Multiple Virtual machines reporting virtual objects with "Unknown" object state in vSAN Skyline health > Virtual objects.
After upgrading vCenter from 6.x/7.x to 7.0 U3c or higher, vSAN Skyline Health > Virtual Objects is reporting objects with "Unknown" object state, the UI shows the VMs names, but these VMs are in another vSAN cluster.
The environment does not have remote storage configured and these VMs do not have VMDKs hosted in the vSAN datastore in question.
- vCenter managing multiple vSAN clusters.
- vCenter upgrade to 7.0U3c or higher.
- Multiple Virtual machines reporting virtual objects with "Unknown" object state in vSAN Skyline health > Virtual objects.
After upgrading vCenter from 6.x/7.x to 7.0 U3c or higher, vSAN Skyline Health > Virtual Objects is reporting objects with "Unknown" object state, the UI shows the VMs names, but these VMs are in another vSAN cluster.
The environment does not have remote storage configured and these VMs do not have VMDKs hosted in the vSAN datastore in question.
Environment
VMware vSAN 7.0.x
Cause
The VMs have an ISO file attached as a virtual CDROM from a different vSAN datastore
Resolution
- Run grep -i iso <vm_name>.vmx
- If you find an ISO file attached belonging to a different vSAN datastore detach the ISO file from the virtual machine configuration
- If you find an ISO file attached belonging to a different vSAN datastore detach the ISO file from the virtual machine configuration
Additional Information
Impact/Risks:
There is no production impact, this is a cosmetic issue seen in vCenter.
There is no production impact, this is a cosmetic issue seen in vCenter.
Feedback
Yes
No
Powered by
