OCPBUGS-76327: Fix flakiness in MutableCSINodeAllocatableCount test

[Phaow]

• Fix flakiness in MutableCSINodeAllocatableCount test, ensure operators scale down successfully in order.
  Failure logs
  During 2026-01-29T00:54:37Z  - 2026-01-29T00:54:40Z  the ebs csi driver operator pod created again and the clustercsidriver seems reconcile back again, the ebs csi driver operator actually does not scale down successfully so the nodeAllocatableUpdatePeriodSeconds reconcile back to 600 . So the next step the CSINodeAllocatableCount does not update in time …

time="2026-01-29T00:54:37Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:d08fdfb20a namespace:openshift-cluster-csi-drivers replicaset:aws-ebs-csi-driver-operator-76548956d7]}" message="{SuccessfulDelete  Deleted pod: aws-ebs-csi-driver-operator-76548956d7-v5w6n map[firstTimestamp:2026-01-29T00:54:37Z lastTimestamp:2026-01-29T00:54:37Z reason:SuccessfulDelete]}"
time="2026-01-29T00:54:37Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:b568ac0a66 namespace:openshift-cluster-csi-drivers replicaset:aws-ebs-csi-driver-operator-76548956d7]}" message="{SuccessfulCreate  Created pod: aws-ebs-csi-driver-operator-76548956d7-mhglr map[firstTimestamp:2026-01-29T00:54:37Z lastTimestamp:2026-01-29T00:54:37Z reason:SuccessfulCreate]}"
time="2026-01-29T00:54:40Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:ff8cd3d029 namespace:openshift-cluster-csi-drivers node:ip-10-0-0-150.us-west-2.compute.internal pod:aws-ebs-csi-driver-operator-76548956d7-mhglr]}" message="{Created  Created container: aws-ebs-csi-driver-operator map[firstTimestamp:2026-01-29T00:54:40Z lastTimestamp:2026-01-29T00:54:40Z reason:Created]}"
time="2026-01-29T00:54:44Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[deployment:aws-ebs-csi-driver-operator hmsg:4b9015bace namespace:openshift-cluster-csi-drivers]}" message="{CSIDriverUpdated  Updated CSIDriver.storage.k8s.io/ebs.csi.aws.com because it changed map[firstTimestamp:2026-01-29T00:54:44Z lastTimestamp:2026-01-29T00:54:44Z reason:CSIDriverUpdated]}"while the scaled down finished at I0129 00:54:37.666658 7927 mutable_csinode_allocatable.go:581] Successfully scaled down aws-ebs-csi-driver-operator

[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

[openshift-ci-robot]

@Phaow: This pull request references Jira Issue OCPBUGS-76327, which is valid. The bug has been moved to the POST state.

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 ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

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

Details

In response to this:

• Fix flakiness in MutableCSINodeAllocatableCount test, ensure operators scale down successfully in order.
  Failure logs
  During 2026-01-29T00:54:37Z  - 2026-01-29T00:54:40Z  the ebs csi driver operator pod created again and the clustercsidriver seems reconcile back again, the ebs csi driver operator actually does not scale down successfully so the nodeAllocatableUpdatePeriodSeconds reconcile back to 600 . So the next step the CSINodeAllocatableCount does not update in time …

time="2026-01-29T00:54:37Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:d08fdfb20a namespace:openshift-cluster-csi-drivers replicaset:aws-ebs-csi-driver-operator-76548956d7]}" message="{SuccessfulDelete  Deleted pod: aws-ebs-csi-driver-operator-76548956d7-v5w6n map[firstTimestamp:2026-01-29T00:54:37Z lastTimestamp:2026-01-29T00:54:37Z reason:SuccessfulDelete]}"
time="2026-01-29T00:54:37Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:b568ac0a66 namespace:openshift-cluster-csi-drivers replicaset:aws-ebs-csi-driver-operator-76548956d7]}" message="{SuccessfulCreate  Created pod: aws-ebs-csi-driver-operator-76548956d7-mhglr map[firstTimestamp:2026-01-29T00:54:37Z lastTimestamp:2026-01-29T00:54:37Z reason:SuccessfulCreate]}"
time="2026-01-29T00:54:40Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:ff8cd3d029 namespace:openshift-cluster-csi-drivers node:ip-10-0-0-150.us-west-2.compute.internal pod:aws-ebs-csi-driver-operator-76548956d7-mhglr]}" message="{Created  Created container: aws-ebs-csi-driver-operator map[firstTimestamp:2026-01-29T00:54:40Z lastTimestamp:2026-01-29T00:54:40Z reason:Created]}"
time="2026-01-29T00:54:44Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[deployment:aws-ebs-csi-driver-operator hmsg:4b9015bace namespace:openshift-cluster-csi-drivers]}" message="{CSIDriverUpdated  Updated CSIDriver.storage.k8s.io/ebs.csi.aws.com because it changed map[firstTimestamp:2026-01-29T00:54:44Z lastTimestamp:2026-01-29T00:54:44Z reason:CSIDriverUpdated]}"while the scaled down finished at I0129 00:54:37.666658 7927 mutable_csinode_allocatable.go:581] Successfully scaled down aws-ebs-csi-driver-operator

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.

[Phaow]

/test e2e-aws-ovn-single-node-techpreview-serial

[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

[Phaow]

/test e2e-aws-ovn-single-node-techpreview-serial

[openshift-trt]

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: cbc232b

• "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vmware-vsphere-csi-driver-operator should not create excessive watch requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
• "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vsphere-problem-detector-operator should not create excessive watch requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]

[Phaow]

/verified by CI

[openshift-ci-robot]

@Phaow: This PR has been marked as verified by [CI](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/30766/pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-techpreview-serial/2019776902511726592).

Details

In response to this:

/verified by CI

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.

[Phaow]

Hi @jsafrane , could you help take a look when you get a chance? Thank you!

[Phaow]

/assign @jsafrane

[jsafrane]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, Phaow

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/storage/OWNERS [jsafrane]

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

[Phaow]

/retest-required

[Phaow]

/retest-required

[Phaow]

/test okd-scos-images

[Phaow]

/test okd-scos-images

[Phaow]

/test okd-scos-images

[Phaow]

/test okd-scos-images

[openshift-ci]

@Phaow: 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.

[openshift-ci-robot]

@Phaow: Jira Issue Verification Checks: Jira Issue OCPBUGS-76327
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-76327 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

• Fix flakiness in MutableCSINodeAllocatableCount test, ensure operators scale down successfully in order.
  Failure logs
  During 2026-01-29T00:54:37Z  - 2026-01-29T00:54:40Z  the ebs csi driver operator pod created again and the clustercsidriver seems reconcile back again, the ebs csi driver operator actually does not scale down successfully so the nodeAllocatableUpdatePeriodSeconds reconcile back to 600 . So the next step the CSINodeAllocatableCount does not update in time …

time="2026-01-29T00:54:37Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:d08fdfb20a namespace:openshift-cluster-csi-drivers replicaset:aws-ebs-csi-driver-operator-76548956d7]}" message="{SuccessfulDelete  Deleted pod: aws-ebs-csi-driver-operator-76548956d7-v5w6n map[firstTimestamp:2026-01-29T00:54:37Z lastTimestamp:2026-01-29T00:54:37Z reason:SuccessfulDelete]}"
time="2026-01-29T00:54:37Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:b568ac0a66 namespace:openshift-cluster-csi-drivers replicaset:aws-ebs-csi-driver-operator-76548956d7]}" message="{SuccessfulCreate  Created pod: aws-ebs-csi-driver-operator-76548956d7-mhglr map[firstTimestamp:2026-01-29T00:54:37Z lastTimestamp:2026-01-29T00:54:37Z reason:SuccessfulCreate]}"
time="2026-01-29T00:54:40Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[hmsg:ff8cd3d029 namespace:openshift-cluster-csi-drivers node:ip-10-0-0-150.us-west-2.compute.internal pod:aws-ebs-csi-driver-operator-76548956d7-mhglr]}" message="{Created  Created container: aws-ebs-csi-driver-operator map[firstTimestamp:2026-01-29T00:54:40Z lastTimestamp:2026-01-29T00:54:40Z reason:Created]}"
time="2026-01-29T00:54:44Z" level=info msg="event interval matches VsphereConfigurationTestsRollOutTooOften" locator="{Kind map[deployment:aws-ebs-csi-driver-operator hmsg:4b9015bace namespace:openshift-cluster-csi-drivers]}" message="{CSIDriverUpdated  Updated CSIDriver.storage.k8s.io/ebs.csi.aws.com because it changed map[firstTimestamp:2026-01-29T00:54:44Z lastTimestamp:2026-01-29T00:54:44Z reason:CSIDriverUpdated]}"while the scaled down finished at I0129 00:54:37.666658 7927 mutable_csinode_allocatable.go:581] Successfully scaled down aws-ebs-csi-driver-operator

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.

[Phaow]

/cherry-pick release-4.21

[openshift-cherrypick-robot]

@Phaow: new pull request created: #30772

Details

In response to this:

/cherry-pick release-4.21

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.