Skip to content

OCPEDGE-1969: add recovery tests for TNA #30022

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Neilhamza
Copy link
Contributor

@Neilhamza Neilhamza commented Jul 27, 2025

add recovery tests for TNA
update common.go
arbiter e2e run

Signed-off-by: nhamza <nhamza@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 27, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 27, 2025

@Neilhamza: This pull request references OCPEDGE-1969 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

add recovery tests for TNA
update common.go

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 requested review from jeff-roche and pacevedom July 27, 2025 15:13
Signed-off-by: nhamza <nhamza@redhat.com>
Copy link

openshift-trt bot commented Jul 28, 2025

Job Failure Risk Analysis for sha: 1bac549

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling Medium
[bz-openshift-apiserver] clusteroperator/openshift-apiserver should not change condition/Available
This test has passed 97.19% of 4444 runs on release 4.20 [Overall] in the last week.

Open Bugs
openshift-apiserver ClusterOperator should not blip Available=False on brief missing HTTP content-type
pull-ci-openshift-origin-main-e2e-gcp-disruptive IncompleteTests
Tests for this run (107) are below the historical average (144): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-gcp-ovn-techpreview-serial-2of2 Medium
[sig-arch] events should not repeat pathologically for ns/openshift-network-diagnostics
Potential external regression detected for High Risk Test analysis
---
[sig-arch] events should not repeat pathologically for ns/openshift-multus
Potential external regression detected for High Risk Test analysis

@dhensel-rh
Copy link

@Neilhamza Are you splitting out the code in common.go to make it reusable by Arbiter only ?

@Neilhamza
Copy link
Contributor Author

@Neilhamza Are you splitting out the code in common.go to make it reusable by Arbiter only ?

i have splitted the code because it can be reused by any test not just arbiter

@dhensel-rh
Copy link

/lgtm

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

/test e2e-metal-ovn-two-node-arbiter

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 31, 2025

@Neilhamza: This pull request references OCPEDGE-1969 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

add recovery tests for TNA
update common.go
arbiter e2e run

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.

Signed-off-by: nhamza <nhamza@redhat.com>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 31, 2025
@Neilhamza Neilhamza requested a review from eggfoobar July 31, 2025 12:05
@eggfoobar
Copy link
Contributor

/lgtm
/hold

Holding for now until the API gets updated with Arbiter GA

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 5, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 5, 2025
@eggfoobar
Copy link
Contributor

/unhold

API change has been merged in

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 7, 2025
})
})

var _ = g.Describe("[sig-etcd][apigroup:config.openshift.io][OCPFeatureGate:HighlyAvailableArbiter][Suite:openshift/two-node][Disruptive] Recovery when arbiter node is down and master nodes restart", func() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where did this run? I did not see this in the two-node arbitor job.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xueqzhan these tests will be ran on a separate lane most possibly alone
So once this gets merged ill create the lane

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question, these tests are designed to be run as part of the two-node suite. So they won't show up on the regular runs, @Neilhamza will be creating some lanes to utilize them

@xueqzhan
Copy link
Contributor

xueqzhan commented Aug 7, 2025

/lgtm

Copy link
Contributor

openshift-ci bot commented Aug 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhensel-rh, eggfoobar, Neilhamza, xueqzhan

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 Aug 7, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7ccc307 and 2 for PR HEAD 9881db2 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 83a2325 and 1 for PR HEAD 9881db2 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a1328e4 and 0 for PR HEAD 9881db2 in total

@openshift-ci-robot
Copy link

/hold

Revision 9881db2 was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 8, 2025
@Neilhamza
Copy link
Contributor Author

/unhold
/retest-required

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 8, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 391f2e7 and 2 for PR HEAD 9881db2 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7e8f07d and 1 for PR HEAD 9881db2 in total

@Neilhamza
Copy link
Contributor Author

/retest-required

2 similar comments
@Neilhamza
Copy link
Contributor Author

/retest-required

@Neilhamza
Copy link
Contributor Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7e8f07d and 2 for PR HEAD 9881db2 in total

Copy link
Contributor

openshift-ci bot commented Aug 11, 2025

@Neilhamza: 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-ovn-etcd-scaling 1bac549 link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 1bac549 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-azure-ovn-upgrade 1bac549 link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-azure-ovn-etcd-scaling 1bac549 link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-etcd-scaling 1bac549 link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-fips-serial-2of2 1bac549 link false /test e2e-gcp-fips-serial-2of2
ci/prow/e2e-gcp-fips-serial-1of2 1bac549 link false /test e2e-gcp-fips-serial-1of2
ci/prow/e2e-gcp-disruptive 1bac549 link false /test e2e-gcp-disruptive
ci/prow/e2e-openstack-serial 1bac549 link false /test e2e-openstack-serial
ci/prow/e2e-vsphere-ovn-etcd-scaling 1bac549 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-metal-ovn-two-node-arbiter 1bac549 link false /test e2e-metal-ovn-two-node-arbiter
ci/prow/e2e-gcp-ovn-techpreview 9881db2 link false /test e2e-gcp-ovn-techpreview
ci/prow/e2e-aws-ovn-single-node-upgrade 9881db2 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway 9881db2 link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-metal-ipi-serial-2of2 9881db2 link false /test e2e-metal-ipi-serial-2of2
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 9881db2 link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-ovn 9881db2 link false /test e2e-metal-ipi-ovn
ci/prow/e2e-metal-ipi-serial-ovn-ipv6-1of2 9881db2 link false /test e2e-metal-ipi-serial-ovn-ipv6-1of2
ci/prow/e2e-azure 9881db2 link false /test e2e-azure
ci/prow/e2e-metal-ipi-ovn-dualstack 9881db2 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-metal-ipi-serial-1of2 9881db2 link false /test e2e-metal-ipi-serial-1of2
ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2 9881db2 link false /test e2e-metal-ipi-serial-ovn-ipv6-2of2
ci/prow/e2e-hypershift-conformance 9881db2 link false /test e2e-hypershift-conformance
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2 9881db2 link false /test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-metal-ipi-virtualmedia 9881db2 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-aws-proxy 9881db2 link false /test e2e-aws-proxy
ci/prow/e2e-openstack-ovn 9881db2 link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-serial 9881db2 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn 9881db2 link false /test e2e-aws-ovn
ci/prow/e2e-aws-disruptive 9881db2 link false /test e2e-aws-disruptive
ci/prow/e2e-agnostic-ovn-cmd 9881db2 link false /test e2e-agnostic-ovn-cmd

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.

@Neilhamza
Copy link
Contributor Author

/retest-required

Copy link

openshift-trt bot commented Aug 11, 2025

Job Failure Risk Analysis for sha: 9881db2

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-disruptive IncompleteTests
Tests for this run (106) are below the historical average (407): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn IncompleteTests
Tests for this run (102) are below the historical average (2464): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack IncompleteTests
Tests for this run (102) are below the historical average (2573): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-local-gateway IncompleteTests
Tests for this run (102) are below the historical average (2544): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-kube-apiserver-rollout IncompleteTests
Tests for this run (102) are below the historical average (1387): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia IncompleteTests
Tests for this run (102) are below the historical average (2499): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-openstack-ovn IncompleteTests
Tests for this run (102) are below the historical average (2671): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9849104 and 1 for PR HEAD 9881db2 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9849104 and 2 for PR HEAD 9881db2 in total

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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants