Operation aborted due to an unexpected error.
/opt/vmware/h4/cloud/log/cloud.log
on the Cloud Director Replication Management Appliance, you see a similar error:ERROR - [UI__########-####-####-####-############_bw_cm] [task-poller-#] com.vmware.h4.cloud.job.C4BaseJob : vCD task urn:vcloud:task:########-####-####-####-############ failed. Debug info: com.vmware.ssdc.library.exceptions.ManagedObjectNotFoundException: Managed object of type "Folder" with value "group-v##" does not exist., details: [ ########-####-####-####-############ ] Managed object of type "Folder" with value "group-v##" does not exist.
/opt/vmware/vcloud-director/logs/vcloud-container-info.log
on Cloud Director, you can see the similar error:ERROR | Backend-activity-pool-58307 | CreateDiskActivity | [Activity Execution] Uncaught Exception during Activity execution. Recent phase: com.vmware.ssdc.backend.services.impl.CreateDiskActivity$CreateShellVmFolderPhase@18205369 - Handle: urn:uuid:########-####-####-####-############, Current Phase: CreateDiskActivity$CreateShellVmFolderPhase
...java.util.concurrent.ExecutionException: com.vmware.ssdc.library.exceptions.ManagedObjectNotFoundException: Managed object of type "Folder" with value "group-v##" does not exist.
at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:136)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
...
Caused by: com.vmware.ssdc.library.exceptions.ManagedObjectNotFoundException: Managed object of type "Folder" with value "object_name" does not exist.
at com.vmware.ssdc.library.vim.LmVim.Convert(LmVim.java:241)
at com.vmware.ssdc.library.vim.LmVim.Convert(LmVim.java:490)
...
Caused by: (vmodl.fault.ManagedObjectNotFound) {
faultCause = null,
faultMessage = null,
obj = ManagedObjectReference: type = Folder, value = group-v##, serverGuid = null
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
VMware Cloud Director Availability 4.x
This issue occurs because the VM folder that Cloud Director tries to place the placeholder independent disk into no longer exists in vCenter Server.
To validate you are experiencing this issue check the folder MORef in the vCenter Managed Object Browser.
https://vCenter_Address/mob/
https://vCenter_Address/mob/?moid=folder_moref
To resolve this issue, contact VMware Cloud Director Support and note this Article ID (314994) in the problem description. For more information, see How to Submit a Support Request.
For more information on enabling the MOB, see The Managed Object Browser is disabled by default in vSphere 6.x.