|Article Number: 540268||Article Version: 2||Article Type: Break Fix|
ViPR Controller,ViPR Controller Controller 3.6 SP2
The user is unable to provision to any host/cluster associated to a particular vCenter due to a vCenter discovery failure. The "Discovery status" of the vCenter in the VIPR UI displays
VIPR Controller UI error
The "Discovery status" of the vCenter in the VIPR UI displays
When discovering a vCenter, ViPR Controller validates all the cluster hosts and associated initiators in the VIPR-C database against the inventory reported by vCenter.
If there are stale Initiators in the VIPR-C DB (i.e. Initiator entries in the RelationIndex CF that are not in the Initiator CF), the validation fails with a NullPointerException error.
A solution exists for this issue, but intervention from EMC technical support personnel is required.
Support personnel must access your storage system to fix this issue.
Contact the EMC Customer Support Center or your service representative for technical assistance and quote this article ID.
Include the ViPR Controller Order History text as well as logs covering the time frame when you contact EMC for technical assistance.
ViPR Controller log
vipr4 vipr4 controllersvc 2020-01-09 12:21:46,637 [126|vcenter|CS_Discovery|null|74ecd786-a45b-4fe9-ab48-cd8023057f3d] ERROR ComputeSystemDiscoveryEngine.java (line 132) Discovery failed for vCenterServerName [urn:storageos:Vcenter:b6ba08ef-c028-40bb-9676-b9d7919e2e05:vdc1]: java.lang.NullPointerException java.lang.NullPointerException at com.emc.storageos.computesystemcontroller.impl.ComputeSystemHelper.queryInitiators(ComputeSystemHelper.java:143)
ViPR Controller logvipr4 vipr4 controllersvc 2020-01-09 12:21:46,607 [126|vcenter|CS_Discovery|null|74ecd786-a45b-4fe9-ab48-cd8023057f3d] INFO AbstractDiscoveryAdapter.java (line 399) find by vcenter cluster id ClusterName