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

CSI: resolve invalid claim states #11890

Merged
merged 2 commits into from
Jan 27, 2022
Merged

CSI: resolve invalid claim states #11890

merged 2 commits into from
Jan 27, 2022

Commits on Jan 25, 2022

  1. csi: resolve invalid claim states on read 

    It's currently possible for CSI volumes to be claimed by allocations
that no longer exist. This changeset asserts a reasonable state at
the state store level by registering these nil allocations as "past
claims" on any read. This will cause any pass through the periodic GC
or volumewatcher to trigger the unpublishing workflow for those claims.
    @tgross
    tgross committed Jan 25, 2022
    Configuration menu
    Copy the full SHA
    64b1b2c View commit details
    Browse the repository at this point in the history

  2. csi: make feasibility check errors more understandable 

    When the feasibility checker finds we have no free write claims, it
checks to see if any of those claims are for the job we're currently
scheduling (so that earlier versions of a job can't block claims for
new versions) and reports a conflict if the volume can't be scheduled
so that the user can fix their claims. But when the checker hits a
claim that has a GCd allocation, the state is recoverable by the
server once claim reaping completes and no user intervention is
required; the blocked eval should complete. Differentiate the
scheduler error produced by these two conditions.
    @tgross
    tgross committed Jan 25, 2022
    Configuration menu
    Copy the full SHA
    e6d7ff4 View commit details
    Browse the repository at this point in the history