book
Article ID: 325564
calendar_today
Updated On:
Issue/Introduction
Symptoms:
com.vmware.ssdc.util.LMException: Internal Server Error
- Migration fails when it is carried out from cluster/resourcepool A to cluster/resourcepool B or vice versa .
- One of the clusters which was part of the same Provider VDC was decommissioned.
- In the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log file, you see entries similar to:
<timestamp> | DEBUG | task-service-activity-pool-123 | GenericVirtualResourcePool | Returning rp moref://1ab234c5-6d7e-890f-g12h-345ijk678901/ResourcePool#resgroup-12345 for vrp on hub moref://1ab234c5-6d7e-890f-g12h-345ij678901/ResourcePool#resgroup-67890 | requestId=...
...
<timestamp> | ERROR | task-service-activity-pool-123 | FutureUtil | Error waiting for future | requestId=...
java.lang.NullPointerException
at com.vmware.vcloud.placementfacade.impl.PlacementServiceFacadeImpl.getResourcePoolVALRef(PlacementServiceFacadeImpl.java:935)
at com.vmware.vcloud.placementfacade.impl.PlacementServiceFacadeImpl.getDefaultPlacementHubsForOrgVdc(PlacementServiceFacadeImpl.java:997)
...
at java.base/java.lang.Thread.run(Thread.java:829)
Environment
VMware Cloud Director 10.x
Cause
This issue is caused due to incorrect/stale resourcepool reference in the provider VDC table.
Using the above log snippet as an example, the moref expected is resgroup-67890 but the value present will correspond to the resourcepool which was removed/decommissioned(example: resgroup-12121) and is returning the nullpointer exception when the migration is carried out.
Resolution
To resolve this issue, please open a Support Request.
Database modifications are required to update the Provider VDC entries and will require VMware Technical Support assistance.