Error: "com.vmware.ssdc.util.LMException: Internal Server Error" while trying to manage VMs on all tenants after disabling elasticity in a tenant
search cancel

Error: "com.vmware.ssdc.util.LMException: Internal Server Error" while trying to manage VMs on all tenants after disabling elasticity in a tenant

book

Article ID: 410707

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • Disabling elasticity on a tenant in VMware Cloud Director(VCD) results in placement engine issues when managing virtual machines and organization VDCs. Tasks like editing, powering on/off VMs results in Internal Server Error.

  • The following message is observed in the log file /opt/vmware/vcloud-director/logs/vcloud-container-debug.log:

    YYYY-MM-DD##:##:##,910 | DEBUG    | pool-jetty-30             | VdcUtils                       | Deleting records from vrp_rp for vrp <VRP_UUID>, apart from vrp_rp Id <VRP_RP_UUID> | requestId=<REQUEST_UUID>,request=PUT https://vcloud.example.com/api/admin/vdc/<VDC_UUID>,requestTime=###########75,remoteAddress=<IP_ADDRESS>:<PORT>,userAgent=Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:140.0) Gecko/20100...,accept=application/*+json;version 40.0.0-alpha

  • Cloud Director tenant CPU/RAM usage failure. The total resources like CPU and RAM are not visible according to usage, only the storage section is correct.
    In the VCD Provider Portal navigate to Cloud Resources > Organization VDCs. For multiple Org VDCs, the CPU and memory utilization are displayed as 0%, and the Resource Pool count is shown as "0".

Environment

VMware Cloud Director 10.6.x

Cause

It is a known issue in current 10.6.x VCD versions where disabling the elasticity in an OrgvDC removes the "vrp_rp" records from all other organization VDCs.

Resolution

This issue is resolved in VMware Cloud Director version 10.6.1.2

Workaround:

To workaround the issue we can try creating a new fresh new Virtual Machine in the affected OrgVDC. Creation of a new Virtual Machine will update the database and repopulate the missing entries in the VCD database. 

  1. Create a small test vm in the affected VDC
  2. Delete test vm
  3. Retry task

If the issue persists after executing the workaround contact Broadcom Technical Support and note this Knowledge Article ID (410707) in the problem description. For more information, see How to Submit a Support Request