OCPBUGS-80133: Bump google.golang.org/grpc

[sbiradar10]

Tracker: https://redhat.atlassian.net/browse/OCPBUGS-80133

Bump grpc to sustaining grpc fork to avoid go version bump

used below command:
go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.71.3-sec.1

[openshift-ci-robot]

@sbiradar10: This pull request references Jira Issue OCPBUGS-80133, 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 dependent Jira Issue OCPBUGS-80308 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Tracker: https://redhat.atlassian.net/browse/OCPBUGS-80133

Bump grpc to sustaining grpc fork to avoid go version bump

used below command:
go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.71.3-sec.1

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]

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: 34e789e1-05e9-483e-af3f-914a87b9f823

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.}

[sbiradar10]

/test e2e-azure-file-nfs-csi

[openshift-ci]

@sbiradar10: 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.

[mpatlasov]

@sbiradar10 , should this PR wait for similar fix to be merged in 4.18 first?

[sbiradar10]

hey @mpatlasov yes but you can still review this and assign required label. I will do jira refresh once 4.18 is in verified state. Thank you

[mpatlasov]

hey @mpatlasov yes but you can still review this and assign required label.

"assign required label" -- is it /label <sth> <sth>?

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpatlasov, sbiradar10

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:

• OWNERS [mpatlasov]

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

[jkaurredhat]

/label backport-risk-assessed

[jsafrane]

/verified by CI

[openshift-ci-robot]

@jsafrane: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

[kunalmemane]

/jira refresh

[openshift-ci-robot]

@kunalmemane: This pull request references Jira Issue OCPBUGS-80133, 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.

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.

[kunalmemane]

/jira refresh

[openshift-ci-robot]

@kunalmemane: This pull request references Jira Issue OCPBUGS-80133, 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.17.z) matches configured target version for branch (4.17.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-80308 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-80308 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@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.

[openshift-ci-robot]

@sbiradar10: Jira Issue OCPBUGS-80133: Some pull requests linked via external trackers have merged:

• openshift/csi-operator#543

The following pull request, linked via external tracker, has not merged:

• openshift/openstack-cinder-csi-driver-operator#194 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

Tracker: https://redhat.atlassian.net/browse/OCPBUGS-80133

Bump grpc to sustaining grpc fork to avoid go version bump

used below command:
go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.71.3-sec.1

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.