Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 23m default-scheduler Successfully assigned vxflexos/vxflexos-controller-0 to k8s-node-02 Normal Pulled 23m kubelet, k8s-node-02 Container image "quay.azk8s.cn/k8scsi/csi-attacher:v1.0.1" already present on machine Normal Created 23m kubelet, k8s-node-02 Created container Normal Started 23m kubelet, k8s-node-02 Started container Normal Pulled 23m kubelet, k8s-node-02 Container image "quay.azk8s.cn/k8scsi/csi-provisioner:v1.0.1" already present on machine Normal Created 23m kubelet, k8s-node-02 Created container Normal Started 23m kubelet, k8s-node-02 Started container Normal Pulling 23m kubelet, k8s-node-02 pulling image "dockerhub.azk8s.cn/dellemc/csi-vxflexos:v1.1.0" Normal Created 23m kubelet, k8s-node-02 Created container Normal Started 23m kubelet, k8s-node-02 Started container Normal Pulled 23m kubelet, k8s-node-02 Successfully pulled image "dockerhub.azk8s.cn/dellemc/csi-vxflexos:v1.1.0" Warning BackOff 23m (x3 over 23m) kubelet, k8s-node-02 Back-off restarting failed container Normal Pulling 22m (x3 over 23m) kubelet, k8s-node-02 pulling image "quay.azk8s.cn/k8scsi/csi-snapshotter:v1.0.1" Normal Created 22m (x3 over 23m) kubelet, k8s-node-02 Created container Normal Started 22m (x3 over 23m) kubelet, k8s-node-02 Started container Normal Pulled 22m (x3 over 23m) kubelet, k8s-node-02 Successfully pulled image "quay.azk8s.cn/k8scsi/csi-snapshotter:v1.0.1" Warning BackOff 13m (x18 over 21m) kubelet, k8s-node-02 Back-off restarting failed container Warning BackOff 3m6s (x80 over 21m) kubelet, k8s-node-02 Back-off restarting failed container
Back to the original problem of not being able to create the volumesnapshotclass...
The workaround, if you see this, is to re-run the install.vxflexos script. The installation is idempotent and will pick up where left off and create the class.
This will be fixed in a future release of the CSI Driver for VxFlex OS
tssgery
10 Posts
0
June 27th, 2019 10:00
It would be good to get the logs from the controller, via:
kubectl logs -n vxflexos vxflexos-controller-0 driver
ZhangFan4
13 Posts
0
June 26th, 2019 03:00
ZhangFan4
13 Posts
0
June 26th, 2019 03:00
after docker search k8scsi, it created volumesnapshotsclass, but a new issue:
Nodes are ready, but controller not work
[root@k8s-master-01 helm]# kubectl get pods -n vxflexos
NAME READY STATUS RESTARTS AGE
vxflexos-controller-0 2/4 CrashLoopBackOff 22 20m
vxflexos-node-5qfbl 2/2 Running 0 20m
vxflexos-node-c7gtx 2/2 Running 0 20m
vxflexos-node-tt8rx 2/2 Running 0 20m
ZhangFan4
13 Posts
0
July 7th, 2019 22:00
tssgery
10 Posts
0
September 24th, 2019 06:00
Back to the original problem of not being able to create the volumesnapshotclass...
The workaround, if you see this, is to re-run the install.vxflexos script. The installation is idempotent and will pick up where left off and create the class.
This will be fixed in a future release of the CSI Driver for VxFlex OS