-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors when doing concurrent host assisted clones #2550
Comments
Couple of notes from grooming meeting:
|
Also, make some changes to the test to catch kubevirt#2550 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
Also, make some changes to the test to catch kubevirt#2550 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
Also, make some changes to the test to catch kubevirt#2550 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
Also, make some changes to the test to catch #2550 Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Haven't tested this yet, but maybe it's been fixed with the recent populator refactoring? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. /close |
@kubevirt-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What happened:
Host-assisted clone source pods keep erroring when doing concurrent dumb clones.
With 2 concurrent clones it seems to converge slowly to success.
What you expected to happen:
restarts are mostly edge case on host assisted clones
How to reproduce it (as minimally and precisely as possible):
Patch storage profile to do host assisted cloning
# k get storageprofile rook-ceph-block -o yaml selecting docker as container runtime apiVersion: cdi.kubevirt.io/v1beta1 kind: StorageProfile metadata: ... name: rook-ceph-block spec: claimPropertySets: - accessModes: - ReadWriteOnce volumeMode: Filesystem cloneStrategy: copy status: claimPropertySets: - accessModes: - ReadWriteOnce volumeMode: Filesystem cloneStrategy: copy provisioner: rook-ceph.rbd.csi.ceph.com storageClass: rook-ceph-block
source dv yaml
run concurrent clones
Additional context:
Errors:
Environment:
kubectl get deployments cdi-deployment -o yaml
): N/Akubectl version
): N/Auname -a
): N/AThe text was updated successfully, but these errors were encountered: