Skip to content
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

Create the source as an existing PVC, but DV is in use and pods are all reporting errors, still running and stuck and freezing #3435

Open
905049079 opened this issue Sep 14, 2024 · 2 comments
Labels
kind/bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@905049079
Copy link

[root@host1 ~]# kubectl get dv
NAME PHASE PROGRESS RESTARTS AGE
cirros Succeeded 100.0% 55m
cirros-clone CloneInProgress N/A 9m39s
cirros2 Succeeded 100.0% 39m

[root@host1 ~]# kubectl get pod
NAME READY STATUS RESTARTS AGE
cdi-upload-cirros-clone 1/1 Running 0 9m42s
virt-launcher-testvm-sqxll 3/3 Running 0 87m
virt-launcher-vm1-zx9mj 2/2 Running 0 30m

[root@host1 ~]# kubectl -n cdi logs --tail=10 cdi-deployment-69bf869699-fnwtg
{"level":"debug","ts":"2024-09-14T07:16:16Z","logger":"events","msg":"pod default/virt-launcher-vm1-zx9mj using PersistentVolumeClaim cirros","type":"Warning","object":{"kind":"PersistentVolumeClaim","namespace":"default","name":"cirros-clone","uid":"09076d82-59fc-44ca-ad68-ef4f7aed29a1","apiVersion":"v1","resourceVersion":"135533"},"reason":"CloneSourceInUse"}
{"level":"debug","ts":"2024-09-14T07:16:18Z","logger":"controller.clone-controller","msg":"reconciling Clone PVCs","PVC":{"name":"cirros-clone","namespace":"default"}}
{"level":"debug","ts":"2024-09-14T07:16:18Z","logger":"controller.clone-controller","msg":"can't create clone source pod, pvc in use by other pod","namespace":"default","name":"cirros","pod":"virt-launcher-vm1-zx9mj"}
{"level":"debug","ts":"2024-09-14T07:16:18Z","logger":"events","msg":"pod default/virt-launcher-vm1-zx9mj using PersistentVolumeClaim cirros","type":"Warning","object":{"kind":"PersistentVolumeClaim","namespace":"default","name":"cirros-clone","uid":"09076d82-59fc-44ca-ad68-ef4f7aed29a1","apiVersion":"v1","resourceVersion":"135533"},"reason":"CloneSourceInUse"}
{"level":"debug","ts":"2024-09-14T07:16:20Z","logger":"controller.clone-controller","msg":"reconciling Clone PVCs","PVC":{"name":"cirros-clone","namespace":"default"}}
{"level":"debug","ts":"2024-09-14T07:16:20Z","logger":"controller.clone-controller","msg":"can't create clone source pod, pvc in use by other pod","namespace":"default","name":"cirros","pod":"virt-launcher-vm1-zx9mj"}
{"level":"debug","ts":"2024-09-14T07:16:20Z","logger":"events","msg":"pod default/virt-launcher-vm1-zx9mj using PersistentVolumeClaim cirros","type":"Warning","object":{"kind":"PersistentVolumeClaim","namespace":"default","name":"cirros-clone","uid":"09076d82-59fc-44ca-ad68-ef4f7aed29a1","apiVersion":"v1","resourceVersion":"135533"},"reason":"CloneSourceInUse"}
{"level":"debug","ts":"2024-09-14T07:16:22Z","logger":"controller.clone-controller","msg":"reconciling Clone PVCs","PVC":{"name":"cirros-clone","namespace":"default"}}
{"level":"debug","ts":"2024-09-14T07:16:22Z","logger":"controller.clone-controller","msg":"can't create clone source pod, pvc in use by other pod","namespace":"default","name":"cirros","pod":"virt-launcher-vm1-zx9mj"}
{"level":"debug","ts":"2024-09-14T07:16:22Z","logger":"events","msg":"pod default/virt-launcher-vm1-zx9mj using PersistentVolumeClaim cirros","type":"Warning","object":{"kind":"PersistentVolumeClaim","namespace":"default","name":"cirros-clone","uid":"09076d82-59fc-44ca-ad68-ef4f7aed29a1","apiVersion":"v1","resourceVersion":"135533"},"reason":"CloneSourceInUse"}

version:1.60.3

@awels
Copy link
Member

awels commented Sep 16, 2024

Yes this is expected behavior, we do not allow clones while the VM is running. It would make no sense to copy data while it is being modified by a running pod.

@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants