Skip to content

Conversation

@jhadvig
Copy link
Member

@jhadvig jhadvig commented Jun 19, 2025

No description provided.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 19, 2025

@jhadvig: This pull request references CONSOLE-4523 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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 19, 2025
@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 Jun 19, 2025
@openshift-ci openshift-ci bot requested review from TheRealJon and spadgett June 19, 2025 11:12
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig

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 Jun 19, 2025
@jhadvig
Copy link
Member Author

jhadvig commented Jun 19, 2025

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips
/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips-nat-instance

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 19, 2025

@jhadvig: 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-upgrade-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/59c03be0-4cfe-11f0-932d-96ef41c72e4b-0

@jhadvig
Copy link
Member Author

jhadvig commented Jun 23, 2025

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips
/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips-nat-instance

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 23, 2025

@jhadvig: 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-upgrade-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/847664a0-502c-11f0-803f-fe062818902e-0

@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 27, 2025
@openshift-bot
Copy link
Contributor

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 Sep 26, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 29, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

@jhadvig: 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-aws-ovn-single-node 2a239f7 link false /test e2e-aws-ovn-single-node
ci/prow/okd-scos-e2e-aws-ovn 2a239f7 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-azure-ovn-upgrade 2a239f7 link true /test e2e-azure-ovn-upgrade
ci/prow/unit 2a239f7 link true /test unit
ci/prow/e2e-hypershift-conformance 2a239f7 link false /test e2e-hypershift-conformance
ci/prow/e2e-gcp-ovn 2a239f7 link true /test e2e-gcp-ovn
ci/prow/e2e-aws-operator 2a239f7 link true /test e2e-aws-operator
ci/prow/e2e-aws-console 2a239f7 link true /test e2e-aws-console

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
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 30, 2025
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. 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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants