Balazs Varga

Same issue here: ``` syncer 2024-03-28 10:25:48 ERROR filters/wrap.go:54 timeout or abort while handling: method=GET URI="/api/v1/services?allowWatchBookmarks=true&resourceVersion=14537&timeout=6m20s&timeoutSeconds=380&watch=true" audit-ID="e3598946-1fff-4190-b8d4-c8a8ccaa0333" {" component": "vcluster"} ``` with k8s 1.28.4 and vcluster 0.19.5

> @hinewin @SCLogo would you mind providing the config values you used to create the vclusters, so I could try to reproduce as good as possible? Just to see if...

thanks. Let me know if you need anything else

@FabianKramm did you find anything ?

found few more things: found the following erron in syncer: ``` E0115 10:41:09.440703 1 controller.go:329] controller persistent-volume-claim: controllerGroup controllerKind PersistentVolumeClaim: PersistentVolumeClaim klog.ObjectRef{Name:"datadir-mongodb-0", Namespace:"mongo"}: namespace mongo name datadir-mongodb-0: reconcileID "fce4801d-207c-4cef-923d-b2ec26ae9e82": Reconciler...

using velero inside with enabledCSI. the snapshot created successfully, but in syncer I see the following issue: ``` cannot sync virtual object as unmanaged physical object exists with desired name...

can be the possible issue that when velero creates the volumesnapshot then syncer sync the object out to the hostcluster and snapshotter on hostcluster creates the volumesnapshotcontent, and sync that...

new info: ``` error getting handle for DataSource Type VolumeSnapshot by Name volsync-backup-redis-master-src-x-redis-x-backup66: snapshot volsync-backup-redis-master-src-x-redis-x-backup66 not bound ``` I see that during sync the `spec.source.volumeSnapshotContentName` in `volumesnapshot` object and the...

> Hi, sorry for taking a while to reply. Have started and paused trying to repro a few times(having been pulled away to other tasks). I've now since skimmed some...

do you have any ETA about this feature?