CSI Attacher tests fail to work with VolumeAttachments informers

[yuga711]

What happened:
In the PR#91307, the csi-attacher tests failed when setup with VolumeAttachement informers

What you expected to happen:
Tests should have succeeded (please see the analysis below)

How to reproduce it (as minimally and precisely as possible):
After PR#91307, in csi_attacher_test.go, add VolumeAttachment informer while setting up the fake host through NewFakeVolumeHostWithCSINodeName()

Anything else we need to know?:
Analysis/rootcause: The tests fail with timeout in Attach() waiting for an event in the FakeWatcher. The priliminary analysis shows, when the informer is setup, the Attach() is stuck on the watcher/channel before timing out. Suspected the informer may be reading the same channel that the Attach() is waiting on: verified this theory by writing the same event 2 times into the channel. This time the Attach() succeeded and so the tests.

note: In particular, the TestAttacherWithCSIDriver() fails because this test waits for the Attach() to complete. Many other tests do not wait for Attach() completion.

/sig storage
CC @msau42

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Network plugin and version (if this is a network-related bug):
• Others:

[msau42]

/assign @misterikkit

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[msau42]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[yuga711]

After PR #97499, this issue doesn't seem to be relevant. Closing it for now. We can reopen if needed.