Skip to content

[release-4.21] OCPBUGS-74102: Fixes the issue in the test TestKubeletConfigMaxPods when AutoNodeSizing is enabled by default #5567

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
Jan 19, 2026
Merged

[release-4.21] OCPBUGS-74102: Fixes the issue in the test TestKubeletConfigMaxPods when AutoNodeSizing is enabled by default #5567

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
10 changes: 0 additions & 10 deletions test/e2e-2of2/kubeletcfg_test.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,16 +162,6 @@ func runTestWithKubeletCfg(t *testing.T, testName string, regexKey []string, str
}
}

// Get the new node object which should reflect new values for the allocatables
if *kc1.Spec.AutoSizingReserved {
refreshedNode := helpers.GetSingleNodeByRole(t, cs, poolName)

// The value for the allocatable should have changed because of the auto node sizing.
// We cannot predict if the values of the allocatables will increase or decrease,
// as it depends on the configuration of the system under test.
require.NotEqual(t, refreshedNode.Status.Allocatable.Memory().Value(), node.Status.Allocatable.Memory().Value(), "value of the allocatable should have changed")
}

if kc2 != nil {
// create our second kubelet config and attach it to our created node pool
cleanupKcFunc2 := createKcWithConfig(t, cs, kcName2, poolName, &kc2.Spec, "1")
Expand Down