Error "Unable to perform this action. Contact your cloud administrator" when attempting to upload any files to catalog of Cloud Director Tenant
search cancel

Error "Unable to perform this action. Contact your cloud administrator" when attempting to upload any files to catalog of Cloud Director Tenant

book

Article ID: 418894

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • Attempting to upload any media or files to catalog of VMware Cloud Director(VCD) tenant gets stuck at 1% and fails with following error: "Unable to perform this action. Contact your cloud administrator"




  • In /opt/vmware/vcloud-director/logs/vcloud-container-debug.log of VCD cell, you see errors similar to:

     WARN     | task-service-activity-pool-242 | VAppUploadManagerImpl          | Transfer session: #####-#####-#####-#####-#####. Error during content upload: No row with the given identifier exists: [com.vmware.vcloud.common.model.logicalresource.StorageClassProviderVdcLogicalResourceModel#PvdcLogicalResourceID] | requestId=#####-#####-#####-#####-#####,request=POST https://<vcd.example.com>/api/catalog/#####-#####-#####-#####-#####/action/upload,requestTime=1763339934997,remoteAddress=#.#.#.#:####,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+xml;version 40.0.0-alpha vcd=#####-#####-#####-#####-#####,task=#####-#####-#####-#####-##### activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:#####-#####-#####-#####-#####)
    org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.vmware.vcloud.common.model.logicalresource.StorageClassProviderVdcLogicalResourceModel#PvdcLogicalResourceID]
            at org.hibernate.impl.SessionFactoryImpl$2.handleEntityNotFound(SessionFactoryImpl.java:409)
            at org.hibernate.proxy.AbstractLazyInitializer.checkTargetState(AbstractLazyInitializer.java:108)
            at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:97)
            at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:140)
            at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:190)
            at com.vmware.vcloud.common.model.logicalresource.StorageClassProviderVdcLogicalResourceModel_$$_jvst450_91.getStorageClassSettings(StorageClassProviderVdcLogicalResourceModel_$$_jvst450_91.java)
            at com.vmware.ssdc.backend.dao.impl.VdcStorageClassSettingsDaoImpl.getPvdcStorageClassSettings(VdcStorageClassSettingsDaoImpl.java:100)
            at com.vmware.ssdc.backend.dao.impl.VdcStorageClassSettingsDaoImpl.getConfigForVdcLogicalResource(VdcStorageClassSettingsDaoImpl.java:92)
            at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
            at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
            at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
            at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)



Environment

VMware Cloud Director 10.x

 

Cause

This issue occurs due to a mismatch in the Logical Resources, essentially what is defined as the logical link between the physical resources and the provider VDC Resources.

Resolution

To identify mismatch of logical resource ID's, perform the following actions:

  1. SSH to primary VCD database cell and establish connection to database using any one of the following commands:

    db

    or 

    sudo -i -u postgres psql vcloud

  2. Run the below query:

    select plr.name from vdc_logical_resource vlr join prov_vdc_logical_resource plr on vlr.name = plr.name where vlr.prov_vdc_lr_id <> plr.id and vlr.prov_vdc_lr_id not in (select id from prov_vdc_logical_resource);

If any results are returned from the above query, please open a Support Request with Broadcom Technical Support and note this Article ID (418894) in the problem description. For more information, see Creating and managing Broadcom support cases.