Open msau42 opened 4 years ago
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
/remove-lifecycle stale
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
/lifecycle frozen
On Tue, Feb 2, 2021 at 9:52 AM fejta-bot notifications@github.com 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 https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/issues/568#issuecomment-771838665, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIJCBAEY5B3L3D52FG35VMTS5A3WBANCNFSM4PVX6DXQ .
We've fixed some issues regarding idempotent calls, such as https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/pull/563 and https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/pull/527.
It would be good to test this in general so we can catch other issues. Some suggestions: