Bug ID 1085473: Let OMD's controller-level QKView capture information for all kubevirt pods, regardless of which blade they are running on

Last Modified: May 17, 2023

Affected Product(s):
F5OS Velos(all modules)

Known Affected Versions:
F5OS-C 1.3.0, F5OS-C 1.3.1, F5OS-C 1.3.2, F5OS-C 1.5.0, F5OS-C 1.5.1

Opened: Mar 08, 2022

Severity: 3-Major


Because the pods are running on the blades, the controller-level QKView does not collect any kubevirt log information, and the partition-level QKViews are not always guaranteed to collect kubevirt logs.


VELOS QKViews do not always collect desired data, potentially resulting in more requests for information in addition to QKView files.


Before this fix: controller-level qkview(No kubevirt logs have been collected) partition-level qkview(It is not guaranteed that kubevirt logs have been collected)


Use command to check information manually: step 1: Query all the pods in kubvirt namespace and print the first item in the line(pod name) oc get pods -n kubevirt -o wide|grep -v NAME| awk '{print$1}' step 2: Get all information about the pod you want oc -n kubevirt describe pod/<pod name>

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips