NO-JIRA: remove extra character

[dhensel-rh]

/test/extended/two_node/tnf_recovery.go had an extra character in job should recover from network disruption with etcd member re-addition. This removes the extra character

[openshift-ci-robot]

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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c28d9e12-994b-4b0e-acb4-344e2d795c07

📥 Commits

Reviewing files that changed from the base of the PR and between 0509de9 and 76da890.

📒 Files selected for processing (1)

• test/extended/two_node/tnf_recovery.go

---

Walkthrough

A test registration label in a Ginkgo test was changed from FIt (focused test) to It (normal spec) in the network disruption recovery scenario. This allows the test to execute with other tests instead of running exclusively. No logic or assertions were modified.

Changes

Cohort / File(s)	Summary
Test Registration test/extended/two_node/tnf_recovery.go	Changed Ginkgo test registration from g.FIt(...) to g.It(...), enabling the network disruption recovery spec to run normally instead of being marked as focused/filtered.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.11.3)

Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions
The command is terminated due to an error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[eggfoobar]

/lgtm

[openshift-ci-robot]

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

[dhensel-rh]

/payload-job periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview

[openshift-ci]

@dhensel-rh: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-main-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/da2f7150-26e3-11f1-9d89-4636371f089c-0

[stbenjam]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• test/extended/two_node/OWNERS [eggfoobar,stbenjam]

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

[eggfoobar]

/retitle NO-JIRA: remove extra character
/verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30920-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview/2036151014792368128

[openshift-ci-robot]

@dhensel-rh: This pull request explicitly references no jira issue.

Details

In response to this:

/test/extended/two_node/tnf_recovery.go had an extra character in job should recover from network disruption with etcd member re-addition. This removes the extra character

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]

@eggfoobar: This PR has been marked as verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30920-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview/2036151014792368128.

Details

In response to this:

/retitle NO-JIRA: remove extra character
/verified by https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30920-nightly-4.22-e2e-metal-ovn-two-node-fencing-techpreview/2036151014792368128

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.

[dhensel-rh]

/pj-rehearse ack

[eggfoobar]

/retest-required

[openshift-ci]

@dhensel-rh: all tests passed!

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.