Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backport of CSI: ensure initial unpublish state is checkpointed into release/1.2.x #14717

Merged
merged 1 commit into from
Sep 27, 2022
Merged

Backport of CSI: ensure initial unpublish state is checkpointed into release/1.2.x #14717

merged 1 commit into from
Sep 27, 2022

Commits on Sep 27, 2022

  1. CSI: ensure initial unpublish state is checkpointed (#14675) 

    A test flake revealed a bug in the CSI unpublish workflow, where an unpublish
that comes from a client that's successfully done the node-unpublish step will
not have the claim checkpointed if the controller-unpublish step fails. This
will result in a delay in releasing the volume claim until the next GC.

This changeset also ensures we're using a new snapshot after each write to raft,
and fixes two timing issues in test where either the volume watcher can
unpublish before the unpublish RPC is sent or we don't wait long enough in
resource-restricted environements like GHA.
    @tgross
    tgross committed Sep 27, 2022
    Configuration menu
    Copy the full SHA
    b40c5c5 View commit details
    Browse the repository at this point in the history