-
Notifications
You must be signed in to change notification settings - Fork 272
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
cdi fails to clone filesystem #3119
Comments
Hey, thanks for reporting this! I think if you increase the CDI log verbosity with https://github.com/kubevirt/containerized-data-importer/blob/release-v1.58/doc/debug.md#log-verbosity May be a similar issue to #2982 |
@Smithx10 If you'd still like to pursue this issue could you please retry with more verbosity? |
I'm running into OOMKilled w/ 32Gi RAM |
So the import/clone/upload pods have a request/limit set on them, and you get OOM killed if you go over that limit. See https://github.com/kubevirt/containerized-data-importer/blob/main/doc/quota.md on how to modify that limit. In most cases it should not be an issue, but we are seeing that slow storage has the ability to exhaust that memory because the OS is caching the writes in memory that counts against that limit. |
@awels I've tried the example, and PR submitted for what the CDI components that worked for me, however still testing the overall process |
I did get farther, however I received |
for vm1_pvc.yml I get failed to create virtual machine pod: pods "virt-launcher-vm1-r6rvd" is forbidden: failed quota: mem-cpu-demo: must specify limits.cpu for: compute; limits.memory for: compute |
Is there quota/limitrange on the namespace? In that case, you would have to specify requests/limits on the VM resource |
@cccsss01 hey, did you get a chance to try this since? specifically interested if there were some limits on the namespace |
There was no quota limitrange on the namespace, however, specifying the requests/limits worked. |
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-sigs/prow repository. |
Attempting to import and use Fedora from Example:
I import Fedora
I than Define a VM see definition below... and it attempts to clone the PV
Source pod log failing
#cdi upload logs
mounts where the Pod is attempting to write "disk.img"
I have the following Defined:
root@rke2-s0:~# kubectl version
Client Version: v1.29.0+rke2r1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.0+rke2r1
VM Definition
DataVolume Source
Storage Profile
Storage Classes
#Kubernetes version
#CDI Deployment
The text was updated successfully, but these errors were encountered: