Bug ID 1166061: Docker logs may not be collected by QKView if container has failed

Last Modified: Aug 01, 2024

Affected Product(s):
F5OS F5OS-A(all modules)

Known Affected Versions:
F5OS-A 1.3.0, F5OS-A 1.3.1, F5OS-A 1.3.2

Fixed In:
F5OS-A 1.7.0

Opened: Sep 30, 2022

Severity: 4-Minor

Symptoms

QKView collects diagnostics from containers on a VELOS system, but sometimes the container may be in an error state where QKView may be unable to interact. It would be useful to collect the Docker logs for failed containers, if available. Prior to this fix, Docker logs for a failed container would not be collected.

Impact

Docker logs will not be collected for failed containers.

Conditions

QKView is run, while a container is in a failed state.

Workaround

Manually perform the command "docker logs <container-name>" for the failed container.

Fix Information

Docker logs for containers will be collected by QKView regardless of the container state.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips