Error : "No row with the given identifier exists: [com.vmware.vcloud.common.model.logicalresource.VdcLogicalResourceModel....]" when managing a vApp

Products

• VMware Cloud Director

Issue/Introduction

• Editing or deleting a vApp from VMware Cloud Director (VCD) fails with an error similar to:

No row with the given identifier exists: [com.vmware.vcloud.common.model.logicalresource.VdcLogicalResourceModel###########-####-####-######]

• The /opt/vmware/vcloud-director/logs/vcloud-container-debug.log on the Cloud Director Cells show errors of the form:

ERROR    | pool-jetty-###       | DefaultExceptionMapper         | Internal server exception | requestId=###########-####-####-####-#######,request=DELETE https://vcloud.example.com/api/vApp/vapp-###########-####-####-####-#######,requestTime=###,remoteAddress=###.###.###.###:port,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/###.## ...,accept=application/*+xml;version 36.3
org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.vmware.vcloud.common.model.logicalresource.VdcLogicalResourceModel############-####-####-####-#######]
        at org.hibernate.impl.SessionFactoryImpl$#.handleEntityNotFound(SessionFactoryImpl.java:###)
        at org.hibernate.proxy.AbstractLazyInitializer.checkTargetState(AbstractLazyInitializer.java:###)
        at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:##)
        at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:###)
        at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:###)
        at com.vmware.vcloud.common.model.logicalresource.VdcLogicalResourceModel_$$_jvste##_#a#.createEntityRef(VdcLogicalResourceModel_$$_jvste##_#a#.java)
        at com.vmware.ssdc.backend.services.impl.VmManagerImpl.getDiskStorageClasses(VmManagerImpl.java:####)

Environment

VMware Cloud Director 10.x

Cause

1. This issue occurs if there is a reference in the Cloud Director database for a VM Disk pointing to a Storage Policy which no longer exists in the Organization VDC where the VM is located.
   A VM Disk should point to a valid Storage Policy in the Organization VDC if the VM Disk is NOT using the VM default policy option but has a specific Storage Policy set. This can be the same as the VM Home Storage Policy (VMX file location) or another different Storage Policy.
2. Issue can also happen if there is no storage policy assigned to the Organization VDC due to database manipulation
   

Resolution

To resolve issue A, contact Broadcom Support and note this Article ID (325508) in the problem description. For more information, see Creating and managing Broadcom support cases.

To resolve issue B, please revert your vCloud director to the latest known backup before making the changes