-
Bug
-
Resolution: Done-Errata
-
Undefined
-
Logging 5.8.z, Logging 5.9.z
-
False
-
None
-
False
-
NEW
-
NEW
-
Fixed an issue which prevented pods from being selectable if they no longer exist, even if they had generated logs.
-
Bug Fix
-
-
Description of problem:
Version-Release number of selected component (if applicable):
5.8
How reproducible:
Always
Steps to Reproduce:
- With LokiStack and CLO installed
- Navigate to the admin console logs
- Try to select from the dropdown pods that created log entries but no longer exists (e.g. deployment restart rollout)
Actual results:
Pods that no longer exist are not listed even if they generated logs in the selected time range
Expected results:
Pods that generated logs are included in the dropdown so the log data can be listed
Additional info:
The dev console already uses the Loki API due to namespaces permission
- clones
-
LOG-5287 Console label queries should use Loki API instead of k8s API
- Closed
- is cloned by
-
LOG-5698 [release-5.8] Console label queries should use Loki API instead of k8s API
- Closed
- links to
-
RHSA-2024:4333 security update Logging for Red Hat OpenShift - 5.9.4