OCPBUGS-22616: [release-4.14] Bump go.opentelemetry.io dependencies

[ankitathomas]

No description provided.

[openshift-ci-robot]

@ankitathomas: This pull request references Jira Issue OCPBUGS-22616, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Obsolete) instead
• expected dependent Jira Issue OCPBUGS-25399 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

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 kubernetes/test-infra repository.

[ankitathomas]

/jira refresh

[openshift-ci-robot]

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

8 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-24451 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 bug Jira Issue OCPBUGS-25399 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-24451 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
• dependent Jira Issue OCPBUGS-25399 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
• bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

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 kubernetes/test-infra repository.

[ncdc]

@ankitathomas please update your commit message to start with UPSTREAM: . Is there a corresponding PR to operator-framework/operator-controller that makes/made this change? We'd want the prefix to be UPSTREAM: 1234 with 1234 being replaced with whatever the upstream PR was. If there isn't an upstream PR, we should probably have one?

[oceanc80]

/label backport-risk-assessed

[openshift-ci]

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

[Xia-Zhao-rh]

/label qe-approved

[openshift-ci-robot]

@ankitathomas: This pull request references Jira Issue OCPBUGS-22616, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-24453 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-24453 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
• bug has dependents

Requesting review from QA contact:
/cc @Xia-Zhao-rh

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 kubernetes/test-infra repository.

[Xia-Zhao-rh]

/label cherry-pick-approved

[m1kola]

Is there a corresponding PR to operator-framework/operator-controller that makes/made this change? We'd want the prefix to be UPSTREAM: 1234 with 1234 being replaced with whatever the upstream PR was. If there isn't an upstream PR, we should probably have one?

We have operator-framework/operator-controller#557 which bumps go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp amongst other things. However it doesn't look like we will be able to cherry-pick the relevant commit into 4.14 downstream branch.

As far as I understand, in this case it should be a <carry> (as it is right now). So it looks good to me.

/lgtm

[awgreene]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ankitathomas, awgreene, m1kola

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 [awgreene]

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]

@ankitathomas: Jira Issue OCPBUGS-22616: All pull requests linked via external trackers have merged:

• openshift/operator-framework-operator-controller#58

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

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 kubernetes/test-infra repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-olm-operator-controller-container-v4.14.0-202312211913.p0.gd714b46.assembly.stream for distgit ose-olm-operator-controller.
All builds following this will include this PR.