-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.16
Description of problem:
When a QEMU pod exits with error status ,but it still exists essome QEMU related logs,the IO won't gather these QEMU ralated logs from error pod.
Version-Release number of selected component (if applicable):
How reproducible:
1. Install openshift-virtualization operator.
2. Use the following yaml file to create the VMI with its pod exits as Error status.
apiVersion: kubevirt.io/v1 kind: VirtualMachineInstance metadata: name: vmi-error-example namespace: test-vm spec: terminationGracePeriodSeconds: 0 domain: devices: disks: - name: containerdisk disk: bus: virtio resources: requests: memory: 64Mi volumes: - name: containerdisk containerDisk: image: quay.io/openshifttest/busybox:latest command: ["/bin/sh", "-c", "kill -SIGSEGV 1"]
3. Trigger IO gathering.
4. Check if the Insights archive includes the QUME logs from above error pod.
Steps to Reproduce:
1. Install openshift-virtualization operator.
2. Use the following yaml file to create the VMI with its pod exits as Error status.
apiVersion: kubevirt.io/v1 kind: VirtualMachineInstance metadata: name: vmi-error-example namespace: test-vm spec: terminationGracePeriodSeconds: 0 domain: devices: disks: - name: containerdisk disk: bus: virtio resources: requests: memory: 64Mi volumes: - name: containerdisk containerDisk: image: quay.io/openshifttest/busybox:latest command: ["/bin/sh", "-c", "kill -SIGSEGV 1"]
3. Trigger IO gathering.
4. Check if the Insights archive includes the QUME logs from above error pod.
Actual results:
4. The insights archive should include the QEMU info gathered from the error pod.
Expected results:
4. The insights archive didn't gather QEMU info from error pod.
Additional info:
