[release-5.0] OCPBUGS-114736: Fix node replacement test timestamp filter and allow job retry

[openshift-cherrypick-robot]

This is an automated cherry-pick of #31492

/assign jaypoulz

/cherrypick release-4.22

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 58175b90-d526-4ef4-b9b6-129aae8dd26f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• test/extended/edge_topologies/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-112390 has been cloned as Jira Issue OCPBUGS-114736. Will retitle bug to link to clone.
/retitle [release-5.0] OCPBUGS-114736: Fix node replacement test timestamp filter and allow job retry

Details

In response to this:

This is an automated cherry-pick of #31492

/assign jaypoulz

/cherrypick release-4.22

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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-114736, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-112390 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #31492

/assign jaypoulz

/cherrypick release-4.22

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-merge-bot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-metal-ovn-two-node-arbiter
/test e2e-metal-ovn-two-node-fencing
/test e2e-metal-ovn-two-node-fencing-recovery

[redhat-chai-bot]

/override ci/prow/e2e-gcp-ovn

Automated triage: This failure appears unrelated to the PR changes.

Rationale: The blocking failure is an upstream [sig-node] NodeConformance container-probe test: the HTTP probe timed out and the container restarted once, while the test expected zero restarts. PR #31577 changes only edge-topology/TNF node-replacement test code and etcd test utilities; it does not touch kubelet probe behavior or the container-probe test.

Evidence:

• e2e-gcp-ovn-upgrade, e2e-gcp-csi, e2e-vsphere-ovn, unit, lint, verify, and image checks passed on the same SHA.
• The failed job recorded 1 blocking failure, 2 informing failures, 2321 passing tests, and 0 flaky tests.
• The release-5.0 test report for this exact test shows 33 failures in 2315 runs (98.57% pass rate), consistent with a recurring low-frequency failure pattern.

If you disagree with this assessment, /retest ci/prow/e2e-gcp-ovn to re-run the job.

---

AI-generated. Review for accuracy.

[openshift-ci]

@redhat-chai-bot: Overrode contexts on behalf of redhat-chai-bot: ci/prow/e2e-gcp-ovn

Details

In response to this:

/override ci/prow/e2e-gcp-ovn

Automated triage: This failure appears unrelated to the PR changes.

Rationale: The blocking failure is an upstream [sig-node] NodeConformance container-probe test: the HTTP probe timed out and the container restarted once, while the test expected zero restarts. PR #31577 changes only edge-topology/TNF node-replacement test code and etcd test utilities; it does not touch kubelet probe behavior or the container-probe test.

Evidence:

• e2e-gcp-ovn-upgrade, e2e-gcp-csi, e2e-vsphere-ovn, unit, lint, verify, and image checks passed on the same SHA.
• The failed job recorded 1 blocking failure, 2 informing failures, 2321 passing tests, and 0 flaky tests.
• The release-5.0 test report for this exact test shows 33 failures in 2315 runs (98.57% pass rate), consistent with a recurring low-frequency failure pattern.

If you disagree with this assessment, /retest ci/prow/e2e-gcp-ovn to re-run the job.

---

AI-generated. Review for accuracy.

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]

@openshift-cherrypick-robot: 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-metal-ovn-two-node-fencing	125aaca	link	false	/test e2e-metal-ovn-two-node-fencing
ci/prow/e2e-gcp-ovn	125aaca	link	true	/test e2e-gcp-ovn
ci/prow/e2e-metal-ovn-two-node-fencing-recovery	125aaca	link	false	/test e2e-metal-ovn-two-node-fencing-recovery
ci/prow/e2e-metal-ovn-two-node-arbiter	125aaca	link	false	/test e2e-metal-ovn-two-node-arbiter

Full PR test history. Your PR dashboard.

Details

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.