/opt/vmware/voss/log/ose-default.log also 5 minutes apart with debug logging enabled:2026-02-06 11:15:04 [ForkJoinPool-2-worker-1] DEBUG c.v.voss.service.async.AsyncTasks - Start async task com.vmware.voss.handler.impl.action.AsyncObjectsAction@########2026-02-06 11:15:04 [ForkJoinPool-2-worker-1] DEBUG c.v.v.h.i.action.TenantAwareAction - Start sync task com.vmware.voss.handler.impl.action.AsyncObjectsAction@########2026-02-06 11:20:36 [ForkJoinPool-2-worker-1] DEBUG c.v.v.h.i.action.TenantAwareAction - End sync task com.vmware.voss.handler.impl.action.AsyncObjectsAction@########2026-02-06 11:20:36 [ForkJoinPool-2-worker-1] DEBUG c.v.voss.service.async.AsyncTasks - End async task com.vmware.voss.handler.impl.action.AsyncObjectsAction@########This issue occurs due to how OSE interacts with its PostgreSQL database during the sync operation on an empty bucket.
This is a known issue affecting VMware Cloud Director Object Storage Extension 3.x
Engineering are aware of this and are actively evaluating a fix for a future release of the product.
Subscribe this knowledge article to get updates on this issue.