Skip to content

[release-4.22] OCPBUGS-83556: Fix EventOutCh deadlock by making publish non-blocking#664

Merged
jzding merged 1 commit intoredhat-cne:release-4.22from
openshift-cherrypick-robot:cherry-pick-663-to-release-4.22
Apr 16, 2026
Merged

[release-4.22] OCPBUGS-83556: Fix EventOutCh deadlock by making publish non-blocking#664
jzding merged 1 commit intoredhat-cne:release-4.22from
openshift-cherrypick-robot:cherry-pick-663-to-release-4.22

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #663

/assign jzding

PublishEventViaAPI sends to EventOutCh with a blocking channel send.
When ProcessOutChannel (the consumer) is slow due to HTTP POST failures
(e.g., unreachable subscribers), the 100-slot buffer fills up and the
next publish blocks forever. This deadlocks the processMessages
goroutine, freezing socket I/O and causing cloud-event-proxy to hang
silently.

Fix by using select with default to drop events when the channel is
full instead of blocking indefinitely. Dropped events are logged as
warnings and counted as failures in metrics.

Signed-off-by: Jack Ding <jackding@gmail.com>
@openshift-ci openshift-ci Bot requested review from nocturnalastro and rdavid April 15, 2026 23:48
@jzding jzding changed the title [release-4.22] Fix EventOutCh deadlock by making publish non-blocking OCPBUGS-83556: [release-4.22] Fix EventOutCh deadlock by making publish non-blocking Apr 16, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-83556, which is invalid:

  • expected dependent Jira Issue OCPBUGS-83555 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is ASSIGNED instead

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:

This is an automated cherry-pick of #663

/assign jzding

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.

@jzding jzding changed the title OCPBUGS-83556: [release-4.22] Fix EventOutCh deadlock by making publish non-blocking [release-4.22] OCPBUGS-83556: Fix EventOutCh deadlock by making publish non-blocking Apr 16, 2026
@jzding
Copy link
Copy Markdown
Member

jzding commented Apr 16, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@jzding: This pull request references Jira Issue OCPBUGS-83556, 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 text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-83555 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-83555 targets the "4.23.0" version, which is one of the valid target versions: 4.23.0
  • bug has dependents

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

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

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.

Copy link
Copy Markdown
Contributor

@nocturnalastro nocturnalastro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nocturnalastro, openshift-cherrypick-robot

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:

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

@jzding jzding merged commit 04f3def into redhat-cne:release-4.22 Apr 16, 2026
5 of 6 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-83556: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-83556 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #663

/assign jzding

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.

@jzding
Copy link
Copy Markdown
Member

jzding commented Apr 16, 2026

/cherry-pick release-4.21

@openshift-cherrypick-robot
Copy link
Copy Markdown
Author

@jzding: new pull request created: #665

Details

In response to this:

/cherry-pick release-4.21

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants