Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-33154: Incorrect use of go wait groups #140

Merged
merged 1 commit into from
May 6, 2024

Conversation

squirrd
Copy link
Contributor

@squirrd squirrd commented May 1, 2024

Minor change to the wait group to ensure the controller does not hang.

The wg.Add(1) (line 198) should be moved closer to the function it is waiting for (line 226).

Having a function (that could exit) between wg.add() and the function with the matching wg.done() could lead to a state where the controller hangs, waiting for the wg.done() that is never called.

@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels May 1, 2024
@openshift-ci-robot
Copy link

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @anuragthehatter

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

In response to this:

Minor change to the wait group to ensure the controller does not hang.

The wg.Add(1) (line 198) should be moved closer to the function it is waiting for (line 226).

Having a function (that could exit) between wg.add() and the function with the matching wg.done() could lead to a state where the controller hangs, waiting for the wg.done() that is never called.

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label May 1, 2024
@martinkennelly
Copy link
Contributor

/test e2e-azure-ovn

Unrelated.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 1, 2024
Copy link
Contributor

openshift-ci bot commented May 1, 2024

@squirrd: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security aeab4d8 link false /test security

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

@martinkennelly
Copy link
Contributor

/test e2e-azure-ovn

cluster init failure

@kyrtapz
Copy link
Contributor

kyrtapz commented May 6, 2024

/lgtm
Thanks @squirrd!

Copy link
Contributor

openshift-ci bot commented May 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyrtapz, martinkennelly, squirrd

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

The pull request process is described here

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 6, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 43c7556 into openshift:master May 6, 2024
8 of 9 checks passed
@openshift-ci-robot
Copy link

@squirrd: Jira Issue OCPBUGS-33154: All pull requests linked via external trackers have merged:

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

In response to this:

Minor change to the wait group to ensure the controller does not hang.

The wg.Add(1) (line 198) should be moved closer to the function it is waiting for (line 226).

Having a function (that could exit) between wg.add() and the function with the matching wg.done() could lead to a state where the controller hangs, waiting for the wg.done() that is never called.

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.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cloud-network-config-controller-container-v4.16.0-202405060852.p0.g43c7556.assembly.stream.el9 for distgit ose-cloud-network-config-controller.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.16.0-0.nightly-2024-05-07-025557

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants