Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #128

/assign IshwarKanse

/cherrypick release-0.4

@IshwarKanse
Copy link
Member

/lgtm
/label qe-approved
/label ux-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jul 2, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request explicitly references no jira issue.

In response to this:

This is an automated cherry-pick of #128

/assign IshwarKanse

/cherrypick release-0.4

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 added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 2, 2025
@openshift-ci openshift-ci bot added ux-approved Signifies that UX has signed off on this PR lgtm Indicates that a PR is ready to be merged. labels Jul 2, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IshwarKanse, openshift-cherrypick-robot

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:

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 Jul 2, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 246f1e6 and 2 for PR HEAD 2b7fd10 in total

@IshwarKanse
Copy link
Member

/override ci/prow/upstream-amd64-aws-e2e

@openshift-ci
Copy link

openshift-ci bot commented Jul 2, 2025

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e

In response to this:

/override ci/prow/upstream-amd64-aws-e2e

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

openshift-ci bot commented Jul 2, 2025

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/upstream-amd64-aws-e2e 2b7fd10 link true /test upstream-amd64-aws-e2e

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 40104d4 into openshift:release-1.0 Jul 2, 2025
5 checks passed
@openshift-cherrypick-robot
Copy link
Author

@openshift-cherrypick-robot: new pull request could not be created: failed to create pull request against openshift/distributed-tracing-console-plugin#release-0.4 from head openshift-cherrypick-robot:cherry-pick-129-to-release-0.4: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:release-0.4 and openshift-cherrypick-robot:cherry-pick-129-to-release-0.4"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

This is an automated cherry-pick of #128

/assign IshwarKanse

/cherrypick release-0.4

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.

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-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR ux-approved Signifies that UX has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants