Open Smithx10 opened 5 months ago
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 We should get the actual stdout/stderr of the untar command
May be a similar issue to https://github.com/kubevirt/containerized-data-importer/issues/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
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 Applying the example CDIConfig fails. error: error parsing cdiconfig.yaml: error converting YAML to JSON: yaml: line 9: did not find expected ',' or '}'
I've tried the example, and spec: podResourceRequirements: limits: cpu: "4" memory: "1Gi" requests: cpu: "1" memory: "250Mi" This fails with unknown field "spec.limits", unknown field "spec.requests"
PR submitted for what the CDI components that worked for me, however still testing the overall process
I did get farther, however I received Error io: read/write on closed pipe piping to gzip on the source pod Error Post "https://cdi-upload-tmp-pvc-58b0c7a5-f12b-4b0f-9ef5-471bd95e5fde.default.svc/v1beta1/upload": write tcp 10.0.0.99:51356->10.111.44.190:443: write: connection reset by peer POSTing to https://cdi-upload-tmp-pvc-58b0c7a5-f12b-4b0f-9ef5-471bd95e5fde.default.svc/v1beta1/upload
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
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.
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