Tests for idempotency

[msau42]

We've fixed some issues regarding idempotent calls, such as #563 and #527.

It would be good to test this in general so we can catch other issues. Some suggestions:

• For testing, reduce the sidecar controller timeouts to 1s so that a controller call will always timeout and retry.
• Incorporate more idempotency testing with csi-sanity, such as add repetition loop to test idempotency kubernetes-csi/csi-test#229

[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

[mattcary]

/remove-lifecycle stale

[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

[mattcary]

/lifecycle frozen

…

On Tue, Feb 2, 2021 at 9:52 AM fejta-bot ***@***.***> wrote: 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 <https://github.com/fejta>. /lifecycle stale — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#568 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIJCBAEY5B3L3D52FG35VMTS5A3WBANCNFSM4PVX6DXQ> .