Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 70766
VMware Smart Assurance: After Vcenter discovery in ESM objects like VMs and Hypervisor are missing
Last update date:
3/22/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Vcenter is discovered as Host, children objects of Vcenter are not discovered.Credentials of Vcenter is passed yet after discovery Relationship Objects are empty.
Cause
In the debug enabled ESM domain log, below functions show failed to fetch information(empty details in {}), hence all the relationships are not created. It is due to user permissions issue at Vcenter.FINER: [ESMVCenterDiscovery-<Vcenter Name>] ESMDataCenter::ProcessObject hostsToClusters: {}FINER: [ESMVCenterDiscovery-<Vcenter Name>] ESMDataCenter::ProcessObject netVDSsToDC: {}FINER: [ESMVCenterDiscovery-<Vcenter Name>] ESMDataCenter::ProcessObject dvSwitchToName: {}FINER: [ESMVCenterDiscovery-<Vcenter Name>] ESMDataCenter::ProcessObject hostsToCluster {}
Resolution
Read permissions for the user account should be propagated to the children (sub folders/VMs) in Vcenter.
