Loading...

XML

Word

Printable

Release Note Status:
In Progress
Release Note Type:
Bug Fix
Release Note Text:

Hide
Before this update, removing the OpenShift pull-secret caused excessive telemetry collection failure logs. As a consequence, telemetry errors flooded the journald logs With this release, the telemetry pull secret error rate has been reduced. As a result, telemetry collection messages no longer flood the logs.

Show
Before this update, removing the OpenShift pull-secret caused excessive telemetry collection failure logs. As a consequence, telemetry errors flooded the journald logs With this release, the telemetry pull secret error rate has been reduced. As a result, telemetry collection messages no longer flood the logs.

Description of problem:

I see journald logs are flooded with messages related to Telemetry collection failed: unable to get pull secret: cloud.openshift.com not found

Version-Release number of selected component (if applicable):

4.19

How reproducible:

Always

Steps to Reproduce:

1. Install 4.19 microshift cluster
2. Enable telemetry and remove pull-secret for cloud.openshift.com
3.

Actual results:

 I see journald has messages related to T`elemetry collection failed: unable to get pull secret: cloud.openshift.com not found` every other second.

Expected results:

Message should be logged but the frequency should be reduced may be to one hour ? but not every sec.

Additional info:

Discussion here: https://redhat-internal.slack.com/archives/C03CJTNLKAT/p1750331260018179

blocks

OCPBUGS-59240 journald flooded with logs related to telemetry collection failed every second

is cloned by

OCPBUGS-59240 journald flooded with logs related to telemetry collection failed every second

links to

RHEA-2025:10667 Red Hat build of MicroShift 4.20.0 bug fix and enhancement update