Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NO-JIRA: Skip pods for ns openshift-infra #29534

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

neisw
Copy link
Contributor

@neisw neisw commented Feb 9, 2025

Aggregation failures for gcp-ovn-rt-upgrade due to the namespace openshift-infra showing up in only 1 out of 10 runs.

Sippy shows only the one run currently

Skipping the namespace unless we want to manually add it to the list when missing.

@openshift-ci-robot
Copy link

@neisw: This pull request explicitly references no jira issue.

In response to this:

Aggregation failures for gcp-ovn-rt-upgrade due to the namespace showing up in only 1 out of 10 runs.

Sippy shows only the one run currently

Skipping the namespace unless we want to manually add it to the list when missing.

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 Feb 9, 2025
@openshift-ci openshift-ci bot requested review from p0lyn0mial and sjenning February 9, 2025 13:13
Copy link
Contributor

openshift-ci bot commented Feb 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neisw

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 Feb 9, 2025
@bertinatto
Copy link
Member

/payload-job periodic-ci-openshift-release-master-ci-4.19-e2e-aws-upgrade-ovn-single-node

Using this PR to verify if a networking failure I'm seeing in #29493 is related to that PR.

Copy link
Contributor

openshift-ci bot commented Feb 9, 2025

@bertinatto: 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.19-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3c19c6f0-e710-11ef-9e42-9c677a29896a-0

@neisw
Copy link
Contributor Author

neisw commented Feb 10, 2025

/retest-required

@bertinatto
Copy link
Member

/test e2e-aws-ovn-microshift-serial

Copy link
Contributor

openshift-ci bot commented Feb 12, 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-hypershift-conformance 5896188 link false /test e2e-hypershift-conformance
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 5896188 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-serial 5896188 link false /test e2e-aws-ovn-single-node-serial

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.

@neisw
Copy link
Contributor Author

neisw commented Feb 13, 2025

/test e2e-vsphere-ovn-upi

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants