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

[WIP] Investigate DNS upgrade test success rate #29263

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Thealisyed
Copy link

Investigate DNS upgrade test success rate

@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 Nov 4, 2024
Copy link
Contributor

openshift-ci bot commented Nov 4, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Thealisyed
Once this PR has been reviewed and has the lgtm label, please assign dennisperiquet for approval. For more information see the Kubernetes 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

@Thealisyed
Copy link
Author

/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-kube-apiserver-rollout

@Thealisyed
Copy link
Author

/test e2e-aws-ovn-single-node-upgrade

@Thealisyed
Copy link
Author

/test images

Copy link
Contributor

openshift-ci bot commented Nov 14, 2024

@Thealisyed: 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-upgrade-rollback 39f3f8c link false /test e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-gcp-ovn 39f3f8c link true /test e2e-gcp-ovn
ci/prow/e2e-agnostic-ovn-cmd 39f3f8c link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-single-node-upgrade 39f3f8c link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-openstack-ovn 39f3f8c link false /test e2e-openstack-ovn
ci/prow/e2e-gcp-csi 39f3f8c link false /test e2e-gcp-csi
ci/prow/okd-scos-e2e-aws-ovn 39f3f8c link false /test okd-scos-e2e-aws-ovn

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

Job Failure Risk Analysis for sha: 39f3f8c

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade-rollback IncompleteTests
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade Low
[sig-node] static pods should start after being created
This test has passed 73.26% of 187 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

Open Bugs
Static pod controller pods sometimes fail to start [etcd]
---
[sig-node] static pods should start after being created
This test has passed 73.12% of 186 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

Open Bugs
Static pod controller pods sometimes fail to start [etcd]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants