Skip to content

NO-JIRA: Fix OKD featureset test as it should only run if the current featureset is Default #30757

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.

Sign up for GitHub

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

Merged
openshift-merge-bot merged 1 commit into from
Feb 5, 2026
Merged

NO-JIRA: Fix OKD featureset test as it should only run if the current featureset is Default #30757

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions test/extended/apiserver/featuregate_okd.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,11 @@ var _ = g.Describe("[sig-api-machinery][Feature:FeatureGate][OCPFeatureGate:OKD]
fg, err := fgClient.Get(context.Background(), "cluster", metav1.GetOptions{})
o.Expect(err).NotTo(o.HaveOccurred(), "Failed to get cluster FeatureGate")

// Skip if current featureset is not Default - we can only modify featureset from Default
if fg.Spec.FeatureSet != configv1.Default {
g.Skip("Skipping test - featureset can only be changed when current featureset is Default")
}

// Attempt to set OKD featureset using dry-run
fg.Spec.FeatureSet = configv1.OKD
_, err = fgClient.Update(context.Background(), fg, metav1.UpdateOptions{
Expand Down