Free on-demand webinars: Learn how to set up, configure, and get more out of Checkmk – Pick your webinar

Werk #22749: Bazel cache: retry version lookup hourly

Component Checks & agents
Title Bazel cache: retry version lookup hourly
Date Nov 16, 2026
Level Trivial Change
Class Bug Fix
Compatibility Compatible - no manual interaction needed
Checkmk versions & editions
3.0.0b1
Not yet released
Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT
2.5.0p22
Not yet released
Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT

The Bazel remote cache special agent looks up the bazel-remote release tags on GitHub to report version information. If this lookup failed, the agent repeated it on every run. This quickly used up the GitHub limit of 60 unauthenticated requests per hour, and on sites without internet access every run could wait up to 30 seconds for the request to time out. Unexpected answers from GitHub, such as a response that is not JSON or a tag name that is not a version number, crashed the agent.

The agent now waits one hour before it retries a failed lookup, or the configured version cache interval if that is shorter. On unexpected answers it skips the version information instead of crashing; the cache metrics are reported as usual. Tags that are not a version number, such as "latest", are ignored. Older bazel-remote releases are now recognized as well (up to the last 100 tags).

If you run the agent with --debug, it always retries the lookup and shows the error.

This continues the fix from Werk #23009.

To the list of all Werks