-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.21
-
None
-
Quality / Stability / Reliability
-
False
-
-
3
-
None
-
None
-
None
-
Rejected
-
AUTOSCALE - Sprint 278
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
CI E2E tests for the VPA are failing
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Open a PR against https://github.com/openshift/vertical-pod-autoscaler-operator
2. Watch the E2E tests fail
3. Profit
Actual results:
STEP: Checking InPlaceOrRecreate VPA feature gate is enabled for admission controller @ 10/02/25 04:24:24.173 [FAILED] in [BeforeEach] - /tmp/tmp.ChqI5PQtnP/autoscaler/vertical-pod-autoscaler/e2e/v1/common.go:639 @ 10/02/25 04:24:24.193 [PANICKED] in [AfterEach] - /usr/lib/golang/src/runtime/panic.go:262 @ 10/02/25 04:24:24.193 also: [FAIL] [sig-autoscaling] [VPA] [full-vpa] [v1] Pods under VPA with InPlaceOrRecreate update mode [BeforeEach] have cpu requests growing with usage [FG:InPlaceOrRecreate] /tmp/tmp.ChqI5PQtnP/autoscaler/vertical-pod-autoscaler/e2e/v1/common.go:639 [FAIL] [sig-autoscaling] [VPA] [full-vpa] [v1] Pods under VPA with InPlaceOrRecreate update mode [BeforeEach] have memory requests growing with usage [FG:InPlaceOrRecreate] /tmp/tmp.ChqI5PQtnP/autoscaler/vertical-pod-autoscaler/e2e/v1/common.go:639
Expected results:
Additional info: