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.

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

ZFSVolume resource ramains stale in system after deleting pvc #130

Closed
w3aman opened this issue May 22, 2020 · 1 comment · Fixed by #145
Closed

ZFSVolume resource ramains stale in system after deleting pvc #130

w3aman opened this issue May 22, 2020 · 1 comment · Fixed by #145
Assignees
Labels
bug Something isn't working.
Milestone

Comments

@w3aman
Copy link
Contributor

w3aman commented May 22, 2020

What steps did you take and what happened:

  • Deletion of Pending pvc is not cleaning up the zfsvolume resource which still remains in pending state.
devuser@rack2:~$ kubectl get pvc --all-namespaces
No resources found.
devuser@rack2:~$ kubectl get zv -n openebs
NAME                                       ZPOOL   NODE        SIZE         STATUS    FILESYSTEM   AGE
pvc-c35668aa-5415-4efc-9d4f-403d262947b8   aman    k8s-node1   4294967296   Pending   zfs          12m
@w3aman w3aman changed the title ZFSVolume resource ramains stale in system after deleting pending state pvc ZFSVolume resource ramains stale in system after deleting pvc May 22, 2020
@pawanpraka1
Copy link
Contributor

introduced in #121. While fixing #111. I will be reverting the wait, the PVC will be bound immediately, but kubectl get zv -n openebs will show the status of the volume. cc @w3aman

@pawanpraka1 pawanpraka1 self-assigned this Jun 4, 2020
@pawanpraka1 pawanpraka1 added the bug Something isn't working. label Jun 4, 2020
@pawanpraka1 pawanpraka1 added this to the v0.8.0 milestone Jun 4, 2020
@kmova kmova closed this as completed in #145 Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants