Skip to content

Conversation

@vrutkovs
Copy link

@vrutkovs vrutkovs commented Jul 2, 2025

Reverts #2285

@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jul 2, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 2, 2025

@vrutkovs: This pull request references CNTRLPLANE-179 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

Details

In response to this:

Reverts #2285

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 openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 2, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 2, 2025

@vrutkovs: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from benluddy and jerpeter1 July 2, 2025 12:33
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Jul 2, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 2, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vrutkovs
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@neisw
Copy link

neisw commented Jul 2, 2025

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips 10

@openshift-ci
Copy link

openshift-ci bot commented Jul 2, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bf3bbe60-574c-11f0-82d1-6806744337d6-0

@vrutkovs
Copy link
Author

vrutkovs commented Jul 2, 2025

@vrutkovs vrutkovs closed this Jul 2, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 2, 2025

@vrutkovs: The following tests 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/verify-commits 7c04bba link true /test verify-commits
ci/prow/okd-scos-e2e-aws-ovn 7c04bba link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-ovn-upgrade 7c04bba link true /test e2e-gcp-ovn-upgrade

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants