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

k8s storage using rook,delete pv ,pvc then create pvc shows peding #82926

Closed
13567436138 opened this issue Sep 20, 2019 · 4 comments
Closed

k8s storage using rook,delete pv ,pvc then create pvc shows peding #82926

13567436138 opened this issue Sep 20, 2019 · 4 comments
Assignees
Labels
kind/support Categorizes issue or PR as a support question. sig/storage Categorizes an issue or PR as relevant to SIG Storage.

Comments

@13567436138
Copy link

[root@dev3 ~]# kubectl get pv -n dev
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS    CLAIM                                           STORAGECLASS   REASON   AGE
pvc-13628e48-3bf2-4937-a27a-67eacd60223e   1Gi        RWO            Delete           Bound     dev/data-redis-ha-server-1                      rook-block              120m
pvc-26696f09-495a-48e3-b6b4-3f09a0db2f22   1Gi        RWO            Delete           Pending   dev/data-redis-ha-server-2                      rook-block              86s
pvc-3d165940-52ee-45d4-acad-9b4531a17c76   1Gi        RWO            Delete           Bound     harbor/database-data-harbor-harbor-database-0   rook-block              2d1h
pvc-453f1db3-f36b-4d2f-92a0-a211cdfbb068   5Gi        RWO            Delete           Bound     harbor/harbor-harbor-registry                   rook-block              2d1h
pvc-48ce7253-dfea-4b8e-8163-21b48c10e1b4   5Gi        RWO            Delete           Bound     harbor/harbor-harbor-chartmuseum                rook-block              2d1h
pvc-70b07cbb-2cf8-491d-acc1-469db3ce5fdd   1Gi        RWX            Delete           Bound     default/mysql-pv-claim                          rook-block              2d1h
pvc-7dd53428-aa89-4547-9ee5-b58b20c53185   1Gi        RWO            Delete           Bound     dev/data-redis-ha-server-0                      rook-block              123m
pvc-9cba5cb3-bd6d-46cf-8e04-e250f6a4416d   1Gi        RWX            Delete           Bound     mysql/mysql-pv-claim                            rook-block              2d23h
pvc-c122ef23-5555-4c60-b8be-4e98e4743760   1Gi        RWO            Delete           Bound     harbor/data-harbor-harbor-redis-0               rook-block              2d1h
pvc-e177fe36-24b2-4c20-8362-4b9d81da7f8d   1Gi        RWO            Delete           Bound     harbor/harbor-harbor-jobservice                 rook-block              2d1h
[root@dev3 ~]# kubectl get describe pv pvc-26696f09-495a-48e3-b6b4-3f09a0db2f22 
error: the server doesn't have a resource type "describe"
[root@dev3 ~]# kubectl describe pv pvc-26696f09-495a-48e3-b6b4-3f09a0db2f22     
Name:            pvc-26696f09-495a-48e3-b6b4-3f09a0db2f22
Labels:          <none>
Annotations:     pv.kubernetes.io/provisioned-by: rook.io/block
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:    rook-block
Status:          Pending
Claim:           dev/data-redis-ha-server-2
Reclaim Policy:  Delete
Access Modes:    RWO
VolumeMode:      Filesystem
Capacity:        1Gi
Node Affinity:   <none>
Message:         
Source:
    Type:       FlexVolume (a generic volume resource that is provisioned/attached using an exec based plugin)
    Driver:     rook.io/rook-system
    FSType:     
    SecretRef:  nil
    ReadOnly:   false
    Options:    map[image:pvc-26696f09-495a-48e3-b6b4-3f09a0db2f22 pool:replicapool storageClass:rook-block]
Events:         <none>
[root@dev3 ~]# ^C
[root@dev3 ~]# ^C
[root@dev3 ~]# kubectl describe pv pvc-26696f09-495a-48e3-b6b4-3f09a0db2f22 
Name:            pvc-26696f09-495a-48e3-b6b4-3f09a0db2f22
Labels:          <none>
Annotations:     pv.kubernetes.io/provisioned-by: rook.io/block
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:    rook-block
Status:          Pending
Claim:           dev/data-redis-ha-server-2
Reclaim Policy:  Delete
Access Modes:    RWO
VolumeMode:      Filesystem
Capacity:        1Gi
Node Affinity:   <none>
Message:         
Source:
    Type:       FlexVolume (a generic volume resource that is provisioned/attached using an exec based plugin)
    Driver:     rook.io/rook-system
    FSType:     
    SecretRef:  nil
    ReadOnly:   false
    Options:    map[image:pvc-26696f09-495a-48e3-b6b4-3f09a0db2f22 pool:replicapool storageClass:rook-block]
[root@dev3 ~]# kubectl get pvc -n dev
NAME                     STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
data-redis-ha-server-0   Bound    pvc-7dd53428-aa89-4547-9ee5-b58b20c53185   1Gi        RWO            rook-block     143m
data-redis-ha-server-1   Bound    pvc-13628e48-3bf2-4937-a27a-67eacd60223e   1Gi        RWO            rook-block     140m
data-redis-ha-server-2   Lost                                                                          rook-block     21m

@13567436138 13567436138 added the kind/support Categorizes issue or PR as a support question. label Sep 20, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 20, 2019
@13567436138
Copy link
Author

/sig storage

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 20, 2019
@cwdsuzhou
Copy link
Member

see this #74374

seems a similar issue, reason should be the race

@cwdsuzhou
Copy link
Member

/assign

@cwdsuzhou
Copy link
Member

@13567436138 can you show your manifests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Development

No branches or pull requests

3 participants