OCPBUGS-30219: bump otelgrpc to 0.46.0

[grokspawn]

Manual backport cherry-pick of e2e482a

[openshift-ci-robot]

@grokspawn: This pull request references Jira Issue OCPBUGS-30219, which is invalid:

• expected Jira Issue OCPBUGS-30219 to depend on a bug targeting a version in 4.16.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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.

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.

[grokspawn]

/jira refresh

[openshift-ci-robot]

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

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.z) matches configured target version for branch (4.15.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-23823 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-23823 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

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

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]

@grokspawn: This pull request references Jira Issue OCPBUGS-30219, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.z) matches configured target version for branch (4.15.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-23823 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-23823 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

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

In response to this:

Manual backport cherry-pick of e2e482a

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.

[everettraven]

/lgtm

[kevinrizza]

/label backport-risk-assessed

[emmajiafan]

The otelgrpc is still 0.44.0: https://github.com/openshift/operator-framework-olm/pull/712/files#diff-a5e215633ff8e6a4eabb33ba5583967629ba72422d56e9881b3eee83aab1f212L206

[emmajiafan]

/hold

[grokspawn]

good spot, @emmajiafan. Updated, pending ci.

[emmajiafan]

/unhold

[grokspawn]

/retest

[openshift-ci]

@grokspawn: all tests passed!

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.

[everettraven]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, grokspawn

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:

• DOWNSTREAM_OWNERS [grokspawn]

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

[openshift-ci-robot]

@grokspawn: Jira Issue OCPBUGS-30219: All pull requests linked via external trackers have merged:

• openshift/operator-framework-olm#712

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

In response to this:

Manual backport cherry-pick of e2e482a

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.

[grokspawn]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@grokspawn: #712 failed to apply on top of branch "release-4.14":

Applying: bump grpc to 1.60.1, reconnect idle connections (#3147)
.git/rebase-apply/patch:6188: trailing whitespace.
- If you are adding a new file, make sure it has the copyright message template 
.git/rebase-apply/patch:6189: trailing whitespace.
  at the top as a comment. You can copy over the message from an existing file 
.git/rebase-apply/patch:6202: trailing whitespace.
- If you want to fix formatting or style, consider whether your changes are an 
.git/rebase-apply/patch:6203: trailing whitespace.
  obvious improvement or might be considered a personal preference. If a style 
.git/rebase-apply/patch:6204: trailing whitespace.
  change is based on preference, it likely will not be accepted. If it corrects 
warning: squelched 1 whitespace error
warning: 6 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	staging/operator-lifecycle-manager/go.mod
M	staging/operator-lifecycle-manager/go.sum
M	staging/operator-lifecycle-manager/pkg/package-server/provider/registry_test.go
M	staging/operator-lifecycle-manager/test/e2e/util.go
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
Removing vendor/google.golang.org/grpc/resolver_conn_wrapper.go
Removing vendor/google.golang.org/grpc/reflection/grpc_reflection_v1alpha/reflection.proto
Removing vendor/google.golang.org/grpc/internal/grpcutil/target.go
Removing vendor/google.golang.org/grpc/install_gae.sh
Removing vendor/google.golang.org/grpc/balancer_conn_wrappers.go
Removing vendor/github.com/golang/protobuf/protoc-gen-go/descriptor/descriptor.pb.go
Removing vendor/github.com/docker/distribution/.travis.yml
Removing vendor/github.com/docker/distribution/.gometalinter.json
Auto-merging staging/operator-lifecycle-manager/test/e2e/util.go
CONFLICT (content): Merge conflict in staging/operator-lifecycle-manager/test/e2e/util.go
Auto-merging staging/operator-lifecycle-manager/pkg/package-server/provider/registry_test.go
Auto-merging staging/operator-lifecycle-manager/go.sum
CONFLICT (content): Merge conflict in staging/operator-lifecycle-manager/go.sum
Auto-merging staging/operator-lifecycle-manager/go.mod
CONFLICT (content): Merge conflict in staging/operator-lifecycle-manager/go.mod
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 bump grpc to 1.60.1, reconnect idle connections (#3147)
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.14

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build operator-lifecycle-manager-container-v4.15.0-202403111911.p0.g59aa935.assembly.stream.el9 for distgit operator-lifecycle-manager.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.15.0-0.nightly-2024-03-12-010512