Skip to content

OCPBUGS-23062: UPSTREAM: 1047: Revert bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.44.0 to 0.45.0#78

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
jsafrane:revert-otel
Nov 8, 2023
Merged

OCPBUGS-23062: UPSTREAM: 1047: Revert bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.44.0 to 0.45.0#78
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
jsafrane:revert-otel

Conversation

@jsafrane
Copy link

@jsafrane jsafrane commented Nov 8, 2023

This reverts commit 9c5cd27.

It has broken our serial jobs, https://issues.redhat.com/browse/OCPBUGS-23062

…on/net/http/otelhttp from 0.44.0 to 0.45.0

This reverts commit 9c5cd27.

It has broken our serial jobs, https://issues.redhat.com/browse/OCPBUGS-23062
@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 Nov 8, 2023
@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-23062, which is invalid:

  • expected the bug to target the "4.15.0" version, but no target version was set

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:

This reverts commit 9c5cd27.

It has broken our serial jobs, https://issues.redhat.com/browse/OCPBUGS-23062

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-ci openshift-ci bot requested review from dobsonj and mpatlasov November 8, 2023 16:32
@openshift-ci
Copy link

openshift-ci bot commented Nov 8, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 8, 2023
@jsafrane
Copy link
Author

jsafrane commented Nov 8, 2023

/payload-job periodic-ci-openshift-release-master-ci-4.15-e2e-aws-sdn-serial

@openshift-ci
Copy link

openshift-ci bot commented Nov 8, 2023

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

  • periodic-ci-openshift-release-master-ci-4.15-e2e-aws-sdn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d61950c0-7e54-11ee-9ca5-452e56cd9c4f-0

@jsafrane
Copy link
Author

jsafrane commented Nov 8, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 8, 2023
@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-23062, 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.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@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 kubernetes/test-infra repository.

@dobsonj
Copy link
Member

dobsonj commented Nov 8, 2023

/retest

@dobsonj
Copy link
Member

dobsonj commented Nov 8, 2023

/lgtm
/jira refresh

@openshift-ci-robot
Copy link

@dobsonj: This pull request references Jira Issue OCPBUGS-23062, which is valid.

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

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

Details

In response to this:

/lgtm
/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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 8, 2023
@openshift-merge-bot openshift-merge-bot bot merged commit 1f086c1 into openshift:master Nov 8, 2023
@openshift-ci-robot
Copy link

@jsafrane: Jira Issue OCPBUGS-23062: All pull requests linked via external trackers have merged:

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

Details

In response to this:

This reverts commit 9c5cd27.

It has broken our serial jobs, https://issues.redhat.com/browse/OCPBUGS-23062

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-merge-robot
Copy link

Fix included in accepted release 4.15.0-0.nightly-2023-11-13-174800

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build csi-provisioner-container-v4.15.0-202311202349.p0.g1f086c1.assembly.stream for distgit csi-provisioner.
All builds following this will include this PR.

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

5 participants