-
Bug
-
Resolution: Unresolved
-
Normal
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
None
-
None
-
None
-
uShift Sprint 271, uShift Sprint 272
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Due to a race condition, telemetry metrics may not be sent right after start. If the telemetry service comes up before kubelet has had a chance to start running and register itself into apiserver then the metrics will fail to collect. This delays sending metrics for 1h.
Version-Release number of selected component (if applicable):
4.19
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-56518 Telemetry metrics may not be sent after start
-
- Closed
-
- is cloned by
-
OCPBUGS-56518 Telemetry metrics may not be sent after start
-
- Closed
-
- links to
-
RHEA-2025:10667 Red Hat build of MicroShift 4.20.0 bug fix and enhancement update