Skip to content

Conversation

neisw
Copy link
Contributor

@neisw neisw commented Aug 26, 2025

time="2025-08-26T15:44:59Z" level=info msg="Found 559 openshift tests"
time="2025-08-26T15:44:59Z" level=info msg="Found 766 kube tests"
time="2025-08-26T15:44:59Z" level=info msg="Found 2201 storage tests"
time="2025-08-26T15:44:59Z" level=info msg="Found 45 builds tests"
time="2025-08-26T15:44:59Z" level=info msg="Found 4 must-gather tests"

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 26, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 26, 2025

@neisw: This pull request references trt-2257 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.

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.

@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 Aug 26, 2025
Copy link
Contributor

openshift-ci bot commented Aug 26, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@neisw
Copy link
Contributor Author

neisw commented Aug 26, 2025

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-upgrade 10

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 26, 2025
Copy link
Contributor

openshift-ci bot commented Aug 26, 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-ci-4.20-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/173f34b0-8278-11f0-8bd2-f9fa7f699c34-0

@neisw
Copy link
Contributor Author

neisw commented Aug 26, 2025

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 10

Copy link
Contributor

openshift-ci bot commented Aug 26, 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-ci-4.20-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/76a50050-828d-11f0-8b59-3f45164d1c5d-0

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 27, 2025

@neisw: This pull request references trt-2257 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.

In response to this:

time="2025-08-26T15:44:59Z" level=info msg="Found 559 openshift tests"
time="2025-08-26T15:44:59Z" level=info msg="Found 766 kube tests"
time="2025-08-26T15:44:59Z" level=info msg="Found 2201 storage tests"
time="2025-08-26T15:44:59Z" level=info msg="Found 45 builds tests"
time="2025-08-26T15:44:59Z" level=info msg="Found 4 must-gather tests"

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.

@neisw
Copy link
Contributor Author

neisw commented Aug 27, 2025

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-upgrade 10

Copy link
Contributor

openshift-ci bot commented Aug 27, 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-ci-4.20-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/792c9920-82db-11f0-8fd3-1692be05a2bc-0

@neisw neisw marked this pull request as ready for review August 27, 2025 00:19
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 27, 2025
@openshift-ci openshift-ci bot requested review from p0lyn0mial and sjenning August 27, 2025 00:20
@neisw
Copy link
Contributor Author

neisw commented Aug 27, 2025

/retest-required

@smg247
Copy link
Member

smg247 commented Aug 27, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
Copy link
Contributor

openshift-ci bot commented Aug 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neisw, smg247

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

@neisw
Copy link
Contributor Author

neisw commented Aug 27, 2025

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Aug 27, 2025
@neisw
Copy link
Contributor Author

neisw commented Aug 27, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ac88cdc and 2 for PR HEAD 748b654 in total

@neisw
Copy link
Contributor Author

neisw commented Aug 27, 2025

/override ci/prow/e2e-gcp-ovn

known issue outside of this pr

Copy link
Contributor

openshift-ci bot commented Aug 27, 2025

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-gcp-ovn

In response to this:

/override ci/prow/e2e-gcp-ovn

known issue outside of this pr

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.

Copy link
Contributor

openshift-ci bot commented Aug 27, 2025

@neisw: 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/e2e-metal-ipi-virtualmedia 748b654 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-openstack-ovn 748b654 link false /test e2e-openstack-ovn
ci/prow/e2e-aws-disruptive 748b654 link false /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn-dualstack 748b654 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway 748b654 link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 748b654 link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-ovn 748b654 link false /test e2e-metal-ipi-ovn
ci/prow/e2e-gcp-ovn-techpreview-serial-1of2 748b654 link false /test e2e-gcp-ovn-techpreview-serial-1of2
ci/prow/e2e-aws-ovn-single-node-upgrade 748b654 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-ovn-rt-upgrade 748b654 link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2 748b654 link false /test e2e-gcp-ovn-techpreview-serial-2of2

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 7643ddf into openshift:main Aug 28, 2025
36 of 47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants