Skip to content

OCPBUGS-74528: upkeep: remove tna feature gate#10403

Open
eggfoobar wants to merge 1 commit intoopenshift:mainfrom
eggfoobar:upkeep-remove-tna-featuregate
Open

OCPBUGS-74528: upkeep: remove tna feature gate#10403
eggfoobar wants to merge 1 commit intoopenshift:mainfrom
eggfoobar:upkeep-remove-tna-featuregate

Conversation

@eggfoobar
Copy link
Contributor

@eggfoobar eggfoobar commented Mar 17, 2026

TNA (two node arbiter) has been GA for the past couple of releases, this is no longer needed as it is supported as part of the platform by default, and the feature gate will be removed from the API entirely.

API PR update
openshift/api#2759

TNA (two node arbiter) has been GA for the past couple of releases, this is no longer needed as it is supported as part of the platform by default, and the feature gate will be removed from the API entirely.

Signed-off-by: ehila <ehila@redhat.com>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 17, 2026
@openshift-ci-robot
Copy link
Contributor

@eggfoobar: This pull request references Jira Issue OCPBUGS-74528, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jogeo

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

Details

In response to this:

TNA (two node arbiter) has been GA for the past couple of releases, this is no longer needed as it is supported as part of the platform by default, and the feature gate will be removed from the API entirely.

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 a review from jogeo March 17, 2026 19:19
@coderabbitai
Copy link

coderabbitai bot commented Mar 17, 2026

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: 04ea8524-8407-4705-a0e9-6eb46529150b

📥 Commits

Reviewing files that changed from the base of the PR and between 1896803 and 580187b.

📒 Files selected for processing (2)
  • pkg/asset/agent/installconfig.go
  • pkg/types/validation/installconfig.go

Walkthrough

The changes remove feature gate enforcement for Arbiter functionality in installation configuration and validation. Arbiter validation and configuration are now unconditionally processed without requiring the FeatureGateHighlyAvailableArbiter gate to be enabled.

Changes

Cohort / File(s) Summary
Arbiter Feature Gate Removal
pkg/asset/agent/installconfig.go, pkg/types/validation/installconfig.go
Removed FeatureGateHighlyAvailableArbiter gate checks, making Arbiter validation and the "2 (with arbiter)" configuration option available unconditionally. Eliminated conditional feature gate logic and removed the features import dependency.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

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


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

@openshift-ci openshift-ci bot requested review from pawanpinjarkar and tthvo March 17, 2026 19:22
@eggfoobar
Copy link
Contributor Author

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

@eggfoobar: 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-arbiter

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4ade3be0-2237-11f1-8737-6892152f2902-0

Copy link
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 17, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tthvo

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:

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 Mar 17, 2026
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-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.

3 participants