Skip to content

Conversation

@damdo
Copy link
Member

@damdo damdo commented May 30, 2025

@openshift-ci-robot
Copy link

openshift-ci-robot commented May 30, 2025

@damdo: This pull request references TRT-2048 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

Reverts #273 which is the revert of #256

Context: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1748604228528099?thread_ts=1741634385.702679&cid=C01CQA76KMX

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 May 30, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 30, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 9, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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
Contributor

openshift-ci bot commented Jul 10, 2025

@damdo: 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-gcp-capi-techpreview 8c98807 link true /test e2e-gcp-capi-techpreview
ci/prow/e2e-aws-capi-techpreview 8c98807 link true /test e2e-aws-capi-techpreview
ci/prow/e2e-azure-ovn-techpreview 8c98807 link false /test e2e-azure-ovn-techpreview
ci/prow/e2e-metal3-capi-techpreview 8c98807 link false /test e2e-metal3-capi-techpreview
ci/prow/e2e-aws-ovn-techpreview 8c98807 link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-capi-customnoupgrade-migration 8c98807 link true /test e2e-aws-capi-customnoupgrade-migration
ci/prow/e2e-vsphere-capi-techpreview 8c98807 link true /test e2e-vsphere-capi-techpreview
ci/prow/e2e-gcp-ovn-techpreview 8c98807 link true /test e2e-gcp-ovn-techpreview
ci/prow/regression-clusterinfra-cucushift-rehearse-capi-aws-ipi 8c98807 link false /test regression-clusterinfra-cucushift-rehearse-capi-aws-ipi
ci/prow/e2e-openstack-capi-techpreview 8c98807 link true /test e2e-openstack-capi-techpreview
ci/prow/e2e-azure-capi-techpreview 8c98807 link true /test e2e-azure-capi-techpreview
ci/prow/e2e-openstack-ovn-techpreview 8c98807 link true /test e2e-openstack-ovn-techpreview
ci/prow/e2e-azure-ovn-techpreview-upgrade 8c98807 link true /test e2e-azure-ovn-techpreview-upgrade
ci/prow/e2e-aws-ovn-techpreview-upgrade 8c98807 link true /test e2e-aws-ovn-techpreview-upgrade

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

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 9, 2025
@damdo
Copy link
Member Author

damdo commented Oct 9, 2025

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants