-
Bug
-
Resolution: Unresolved
-
Normal
-
4.16.z
Description of problem:
When creating a VMI with its pod that doesn't include any logs, the QEMU logs gathering would be blocked by this pod and gather nothing.
Version-Release number of selected component (if applicable):
4.16.z
How reproducible:
To create a VMI with its pod doesn't include any logs, then trigger the IO gathering.
Steps to Reproduce:
1. Create the VMI via the following conf:
apiVersion: kubevirt.io/v1 kind: VirtualMachineInstance metadata: name: vmi-succeed-fast namespace: test-vm spec: runStrategy: Once terminationGracePeriodSeconds: 0 domain: devices: disks: - name: containerdisk disk: bus: virtio resources: requests: memory: 64Mi volumes: - name: containerdisk containerDisk: image: quay.io/containerdisks/busybox:latest
2. Create a VMI with running status.
3. Trigger the IO gathering.
4. View the IO pod logs, check if there is a log about `"qemu_kubevirt_launcher_logs" failed with the error:`
5. Check the Insights archive includes the qemu log info.
Actual results:
4. The IO pod includes the following error info:
E1014 07:03:48.575665 1 gather.go:140] gatherer "clusterconfig" function "qemu_kubevirt_launcher_logs" failed with the error: container "compute" in pod "virt-launcher-vmi-succeed-fast-b4zbh" is waiting to start: PodInitializing
5. The Insights archive doesn't include any QEMU log info.
Expected results:
4. The IO pod shouldn't include any error about qemu info. 5. The Insights archive should include qemu log info.
Additional info:
