Volume stuck in Pending state forever after a kubectl delete #2409
Assignees
Labels
complexity:easy
Something that requires less than a day to fix
topic:storage
Issues related to storage
Comments
slaperche-scality
added
topic:storage
slaperche-scality
added a commit
that referenced
this issue
Apr 15, 2020
Closes: #2409 Signed-off-by: Sylvain Laperche <sylvain.laperche@scality.com>
slaperche-scality
added a commit
that referenced
this issue
Apr 15, 2020
The way we were handling a deletion while the creation is in progress was buggy. We were correctly detecting that we were creating the volume and thus were postponing the deletion until the creation was done (either with success or not). But we were exiting the reconciliation loop too early and never had a chance to keep continue the volume creation, thus we were forever stuck in a Pending state (and the deletion was posptone forever as well). The fix is easy enough though: in such case we don't exit the reconciliation loop immediatly, to be able to call `deployVolume` and made some progress until we're stabilized. Refs: #2409 Signed-off-by: Sylvain Laperche <sylvain.laperche@scality.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component:
operator
What happened:
When trying to delete a volume whose creation was in progress, the volume stay stuck in Pending state forever.
What was expected:
We let the volume creation proceed until the end (be it with an error or a success) and then the deletion happen.
Steps to reproduce
kubectl apply -f volume.yaml && sleep 1 && kubectl delete -f volume.yamlResolution proposal:
Do not exit the reconciliation loop too early, in order to let
deployVolumemoving the process forward.The text was updated successfully, but these errors were encountered: