-
Notifications
You must be signed in to change notification settings - Fork 258
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
500 error during DV import on GCP env #2836
Comments
Logs from importer pod:
Datavolume definition:
Logs from cdi-upload pod:
|
cdi-deployment logs (it keeps iterating this block for every 0,5 seconds):
|
Sounds like a recent issue we heard about from hypershift folks, You could also enable a cri-o configurable: |
newest cdi contains bug which is causing problems for our tests. kubevirt/containerized-data-importer#2836 Signed-off-by: Karel Simon <ksimon@redhat.com>
newest cdi contains bug which is causing problems for our tests. kubevirt/containerized-data-importer#2836 Signed-off-by: Karel Simon <ksimon@redhat.com>
This issue should now be resolved by the linked cri-o change. @ksimon1 Are you okay if we close this issue now? |
yes, thanks |
What happened:
500 error during DV import on GCP env
The e2e tests created DV with fedora image, then the test created VM from common-template which creates new datavolume, which clones original DV with fedora image. During the import of the VM disk, importer pod throws 500 error.
What you expected to happen:
DV is imported and VM runs
How to reproduce it (as minimally and precisely as possible):
run fedora e2e test in common templates (I can help with setting up env)
Environment:
kubectl get deployments cdi-deployment -o yaml
): v1.56.1kubectl version
):VM definition:
StorageClass
The text was updated successfully, but these errors were encountered: