You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
we found error when deploy Kubernetes connect to disk. detail error as below.
Jun 6 12:15:29 kube-local kubelet[27065]: I0606 12:15:29.036314 27065 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "ibm-ubiquity-db" (UniqueName: "flexvolume-ibm/ubiquity-k8s-flex/ibm-ubiquity-db") pod "ubiquity-db-6f5dcbc87b-gx999" (UID: "7d19746d-8854-11e9-bd4c-0050569f5498")
Jun 6 12:15:29 kube-local kubelet[27065]: E0606 12:15:29.040925 27065 nestedpendingoperations.go:267] Operation for ""flexvolume-ibm/ubiquity-k8s-flex/ibm-ubiquity-db"" failed. No retries permitted until 2019-06-06 12:17:31.040865823 +0000 UTC m=+7597.245369115 (durationBeforeRetry 2m2s). Error: "Volume not attached according to node status for volume "ibm-ubiquity-db" (UniqueName: "flexvolume-ibm/ubiquity-k8s-flex/ibm-ubiquity-db") pod "ubiquity-db-6f5dcbc87b-gx999" (UID: "7d19746d-8854-11e9-bd4c-0050569f5498") "
Jun 6 12:15:29 kube-local kubelet[27065]: E0606 12:15:29.932299 27065 kubelet.go:1657] Unable to mount volumes for pod "ubiquity-db-6f5dcbc87b-gx999_ubiquity(7d19746d-8854-11e9-bd4c-0050569f5498)": timeout expired waiting for volumes to attach or mount for pod "ubiquity"/"ubiquity-db-6f5dcbc87b-gx999". list of unmounted volumes=[ibm-ubiquity-db]. list of unattached volumes=[ibm-ubiquity-db default-token-jsq2j]; skipping pod
Jun 6 12:15:29 kube-local kubelet[27065]: E0606 12:15:29.932387 27065 pod_workers.go:190] Error syncing pod 7d19746d-8854-11e9-bd4c-0050569f5498 ("ubiquity-db-6f5dcbc87b-gx999_ubiquity(7d19746d-8854-11e9-bd4c-0050569f5498)"), skipping: timeout expired waiting for volumes to attach or mount for pod "ubiquity"/"ubiquity-db-6f5dcbc87b-gx999". list of unmounted volumes=[ibm-ubiquity-db]. list of unattached volumes=[ibm-ubiquity-db default-token-jsq2j]
Please help recommend.
Thanks,
Jack
The text was updated successfully, but these errors were encountered:
Hello,
we found error when deploy Kubernetes connect to disk. detail error as below.
Jun 6 12:15:29 kube-local kubelet[27065]: I0606 12:15:29.036314 27065 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "ibm-ubiquity-db" (UniqueName: "flexvolume-ibm/ubiquity-k8s-flex/ibm-ubiquity-db") pod "ubiquity-db-6f5dcbc87b-gx999" (UID: "7d19746d-8854-11e9-bd4c-0050569f5498")
Jun 6 12:15:29 kube-local kubelet[27065]: E0606 12:15:29.040925 27065 nestedpendingoperations.go:267] Operation for ""flexvolume-ibm/ubiquity-k8s-flex/ibm-ubiquity-db"" failed. No retries permitted until 2019-06-06 12:17:31.040865823 +0000 UTC m=+7597.245369115 (durationBeforeRetry 2m2s). Error: "Volume not attached according to node status for volume "ibm-ubiquity-db" (UniqueName: "flexvolume-ibm/ubiquity-k8s-flex/ibm-ubiquity-db") pod "ubiquity-db-6f5dcbc87b-gx999" (UID: "7d19746d-8854-11e9-bd4c-0050569f5498") "
Jun 6 12:15:29 kube-local kubelet[27065]: E0606 12:15:29.932299 27065 kubelet.go:1657] Unable to mount volumes for pod "ubiquity-db-6f5dcbc87b-gx999_ubiquity(7d19746d-8854-11e9-bd4c-0050569f5498)": timeout expired waiting for volumes to attach or mount for pod "ubiquity"/"ubiquity-db-6f5dcbc87b-gx999". list of unmounted volumes=[ibm-ubiquity-db]. list of unattached volumes=[ibm-ubiquity-db default-token-jsq2j]; skipping pod
Jun 6 12:15:29 kube-local kubelet[27065]: E0606 12:15:29.932387 27065 pod_workers.go:190] Error syncing pod 7d19746d-8854-11e9-bd4c-0050569f5498 ("ubiquity-db-6f5dcbc87b-gx999_ubiquity(7d19746d-8854-11e9-bd4c-0050569f5498)"), skipping: timeout expired waiting for volumes to attach or mount for pod "ubiquity"/"ubiquity-db-6f5dcbc87b-gx999". list of unmounted volumes=[ibm-ubiquity-db]. list of unattached volumes=[ibm-ubiquity-db default-token-jsq2j]
Please help recommend.
Thanks,
Jack
The text was updated successfully, but these errors were encountered: