Skip to content

OCPBUGS-79368: google.golang.org/grpc v1.79.3#994

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
jstuever:OCPBUGS-79368
Apr 2, 2026
Merged

OCPBUGS-79368: google.golang.org/grpc v1.79.3#994
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
jstuever:OCPBUGS-79368

Conversation

@jstuever
Copy link
Copy Markdown
Contributor

No description provided.

@openshift-ci-robot 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 Mar 23, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jstuever: This pull request references Jira Issue OCPBUGS-79368, which is invalid:

  • expected dependent Jira Issue OCPBUGS-79367 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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:

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
Copy link
Copy Markdown

coderabbitai bot commented Mar 23, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d3607682-bf00-4223-afc8-aa6e9738bff9

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
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from dlom and suhanime March 23, 2026 18:34
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 23, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 23, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 47.14%. Comparing base (073fed5) to head (2233f74).
⚠️ Report is 4 commits behind head on release-4.20.

Additional details and impacted files

Impacted file tree graph

@@               Coverage Diff                @@
##           release-4.20     #994      +/-   ##
================================================
+ Coverage         46.69%   47.14%   +0.44%     
================================================
  Files                97       97              
  Lines             12005    12204     +199     
================================================
+ Hits               5606     5753     +147     
- Misses             5781     5828      +47     
- Partials            618      623       +5     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jstuever
Copy link
Copy Markdown
Contributor Author

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 26, 2026

@jstuever: you cannot LGTM your own PR.

Details

In response to this:

/lgtm
/approve
/label backport-risk-assessed

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.

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 26, 2026
@jstuever
Copy link
Copy Markdown
Contributor Author

/assign @dlom

@huangmingxia
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-vsphere-ipi-disc-f28

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@huangmingxia: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-vsphere-ipi-disc-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e674bbd0-2992-11f1-9b70-9c89a6706453-0

@huangmingxia
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-nutanix-ipi-multi-nic-f28

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@huangmingxia: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-nutanix-ipi-multi-nic-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f93d1550-2992-11f1-8073-eb202000b9b7-0

@huangmingxia
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-ibmcloud-ipi-disc-priv-f28

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@huangmingxia: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-ibmcloud-ipi-disc-priv-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/07515ca0-2993-11f1-94a7-5e8cc2f6cc9f-0

@huangmingxia
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-gcp-ipi-disc-priv-oidc-fips-mini-perm-f28

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@huangmingxia: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-gcp-ipi-disc-priv-oidc-fips-mini-perm-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/22feeee0-2993-11f1-9d8a-e2f814475e86-0

@huangmingxia
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-azure-stack-ipi-f28

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@huangmingxia: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-azure-stack-ipi-f28

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2d822030-2993-11f1-8ec4-f66e1fb2c226-0

@huangmingxia
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-azure-mag-ipi-fips-f14

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@huangmingxia: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-azure-mag-ipi-fips-f14

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3710df60-2993-11f1-99f6-e3df4d549a6a-0

@huangmingxia
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-azure-ipi-disc-oidc-mini-perm-f14

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@huangmingxia: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-azure-ipi-disc-oidc-mini-perm-f14

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/46a29ef0-2993-11f1-9986-8ee6a3304d1b-0

@huangmingxia
Copy link
Copy Markdown
Contributor

/payload-job periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-aws-ipi-private-shared-vpc-phz-sts-mini-perm-f14

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@huangmingxia: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-aws-ipi-private-shared-vpc-phz-sts-mini-perm-f14

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5732bbb0-2993-11f1-90f8-4d7b7758c819-0

@huangmingxia
Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@huangmingxia: This pull request references Jira Issue OCPBUGS-79368, which is invalid:

  • expected dependent Jira Issue OCPBUGS-79367 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST 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.

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.

@dlom
Copy link
Copy Markdown
Contributor

dlom commented Mar 27, 2026

/lgtm

@huangmingxia
Copy link
Copy Markdown
Contributor

/verified by ci runs

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 30, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@huangmingxia: This PR has been marked as verified by ci runs.

Details

In response to this:

/verified by ci runs

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.

@jstuever
Copy link
Copy Markdown
Contributor Author

/override ci/prow/security

@jstuever
Copy link
Copy Markdown
Contributor Author

/assign @dlom

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 30, 2026

@jstuever: Overrode contexts on behalf of jstuever: ci/prow/security

Details

In response to this:

/override ci/prow/security

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.

@dlom
Copy link
Copy Markdown
Contributor

dlom commented Mar 30, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 30, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dlom, jstuever

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

@huangmingxia
Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@huangmingxia: This pull request references Jira Issue OCPBUGS-79368, which is invalid:

  • expected dependent Jira Issue OCPBUGS-79367 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST 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.

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.

@jstuever
Copy link
Copy Markdown
Contributor Author

jstuever commented Apr 1, 2026

/jira refresh

@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 Apr 1, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jstuever: This pull request references Jira Issue OCPBUGS-79368, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-79367 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-79367 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents

Requesting review from QA contact:
/cc @huangmingxia

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 1, 2026
@openshift-ci openshift-ci bot requested a review from huangmingxia April 1, 2026 21:34
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 2, 2026

@jstuever: 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-merge-bot openshift-merge-bot bot merged commit 92d1035 into openshift:release-4.20 Apr 2, 2026
13 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@jstuever: Jira Issue Verification Checks: Jira Issue OCPBUGS-79368
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-79368 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants