OCPBUGS-112062: fix: use native gRPC probes for CatalogSource pods [release-4.22] by twoGiants · Pull Request #1356 · openshift/operator-framework-olm

twoGiants · 2026-08-19T13:47:10Z

Backport of #1346 to release-4.22.

Replace exec-based grpc_health_probe invocations with native Kubernetes
gRPC probe handlers on CatalogSource pod readiness, liveness, and startup
probes. Dynatrace OneAgent LD_PRELOAD injection causes exec probe timeouts
and CrashLoopBackOff. Native gRPC probes run from kubelet outside the
container, avoiding injection.

Upstream PR: operator-framework/operator-lifecycle-manager#3888

CatalogSource pods use exec probes that fork a grpc_health_probe binary inside the container. Dynatrace OneAgent injects via LD_PRELOAD into forked processes, adding ~6s startup overhead that exceeds the 5s probe timeout, causing CrashLoopBackOff. Switch to Kubernetes native gRPC probes, where kubelet calls the health endpoint directly from outside the container. Native gRPC probes are GA since Kubernetes 1.24. Issue OCPBUGS-74905 Upstream-repository: operator-lifecycle-manager Upstream-commit: 124725122b46c4f02a74aac3a92cf1dfe42f326c

openshift-merge-bot · 2026-08-19T13:47:14Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

openshift-ci-robot · 2026-08-19T13:47:18Z

@twoGiants: This pull request references Jira Issue OCPBUGS-74905, which is invalid:

expected the bug to target either version "4.22.0." or "openshift-4.22.0.", but it targets "5.0.0" instead
expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-74905 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Backport of #1346 to release-4.22.

Replace exec-based grpc_health_probe invocations with native Kubernetes
gRPC probe handlers on CatalogSource pod readiness, liveness, and startup
probes. Dynatrace OneAgent LD_PRELOAD injection causes exec probe timeouts
and CrashLoopBackOff. Native gRPC probes run from kubelet outside the
container, avoiding injection.

Upstream PR: operator-framework/operator-lifecycle-manager#3888

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

coderabbitai · 2026-08-19T13:47:30Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c2f26728-3d6a-4c62-978d-cceaefdd2a8e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

openshift-ci-robot · 2026-08-19T13:50:37Z

@twoGiants: This pull request references Jira Issue OCPBUGS-112062, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-112062 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Backport of #1346 to release-4.22.

Replace exec-based grpc_health_probe invocations with native Kubernetes
gRPC probe handlers on CatalogSource pod readiness, liveness, and startup
probes. Dynatrace OneAgent LD_PRELOAD injection causes exec probe timeouts
and CrashLoopBackOff. Native gRPC probes run from kubelet outside the
container, avoiding injection.

Upstream PR: operator-framework/operator-lifecycle-manager#3888

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

twoGiants · 2026-08-19T13:51:06Z

/jira refresh

openshift-ci-robot · 2026-08-19T13:51:10Z

@twoGiants: This pull request references Jira Issue OCPBUGS-112062, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-112062 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

twoGiants · 2026-08-19T13:52:19Z

/jira refresh

openshift-ci-robot · 2026-08-19T13:52:24Z

@twoGiants: This pull request references Jira Issue OCPBUGS-112062, which is invalid:

expected Jira Issue OCPBUGS-112062 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

twoGiants · 2026-08-19T13:53:40Z

/jira refresh

openshift-ci-robot · 2026-08-19T13:53:48Z

@twoGiants: This pull request references Jira Issue OCPBUGS-112062, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-74905 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-74905 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

twoGiants · 2026-08-19T13:55:09Z

/cherrypick release-4.21

openshift-cherrypick-robot · 2026-08-19T13:55:13Z

@twoGiants: once the present PR merges, I will cherry-pick it on top of release-4.21 in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.21 release-4.20 release-4.19 release-4.18 release-4.17 release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

twoGiants · 2026-08-19T13:56:25Z

/cherrypick release-4.20
/cherrypick release-4.19

openshift-cherrypick-robot · 2026-08-19T13:56:28Z

@twoGiants: once the present PR merges, I will cherry-pick it on top of release-4.19, release-4.20 in new PRs and assign them to you.

Details

In response to this:

/cherrypick release-4.20
/cherrypick release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

twoGiants · 2026-08-19T13:56:56Z

/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16

openshift-cherrypick-robot · 2026-08-19T13:56:59Z

@twoGiants: once the present PR merges, I will cherry-pick it on top of release-4.16, release-4.17, release-4.18 in new PRs and assign them to you.

Details

In response to this:

/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

tmshort · 2026-08-19T14:42:04Z

/lgtm
/approve

openshift-merge-bot · 2026-08-19T14:44:38Z

Scheduling required tests:
/test e2e-aws-olmv0-ext

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console-olm
/test e2e-gcp-olm
/test e2e-gcp-ovn
/test e2e-upgrade

openshift-ci · 2026-08-19T14:44:53Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tmshort, twoGiants

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~DOWNSTREAM_OWNERS~~ [tmshort]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

tmshort · 2026-08-20T21:03:58Z

/test okd-scos-images

openshift-ci · 2026-08-20T21:28:45Z

@twoGiants: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 19, 2026

openshift-ci Bot requested review from fgiudici and tmshort August 19, 2026 13:49

twoGiants changed the title ~~OCPBUGS-74905: fix: use native gRPC probes for CatalogSource pods [release-4.22]~~ OCPBUGS-112062: fix: use native gRPC probes for CatalogSource pods [release-4.22] Aug 19, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 19, 2026

openshift-ci Bot assigned tmshort Aug 19, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 19, 2026

Uh oh!

Conversation

twoGiants commented Aug 19, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

coderabbitai Bot commented Aug 19, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

twoGiants commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

twoGiants commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

twoGiants commented Aug 19, 2026

Uh oh!

openshift-ci-robot commented Aug 19, 2026

Uh oh!

twoGiants commented Aug 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-cherrypick-robot commented Aug 19, 2026

Uh oh!

twoGiants commented Aug 19, 2026

Uh oh!

openshift-cherrypick-robot commented Aug 19, 2026

Uh oh!

twoGiants commented Aug 19, 2026

Uh oh!

openshift-cherrypick-robot commented Aug 19, 2026

Uh oh!

tmshort commented Aug 19, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 19, 2026

Uh oh!

openshift-ci Bot commented Aug 19, 2026

Uh oh!

tmshort commented Aug 20, 2026

Uh oh!

openshift-ci Bot commented Aug 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

twoGiants commented Aug 19, 2026 •

edited

Loading