Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
Solved!
Go to SolutionCannot create volumesnapshotclass in install.vxflexos
[root@k8s-master-01 helm]# sh install.vxflexos
Kubernetes version v1.13.3
Kubernetes master nodes: 192.168.18.10
Kubernetes minion nodes: 192.168.18.11 192.168.18.12
Verifying the SDC installation.
Retrieved 1 mdm(s)
MDM-ID 39f317742b58aa0f SDC ID 749f21df00000004 INSTALLATION ID 5082d8992e46577b IPs [0]-192.168.18.103 [1]-192.168.18.104
Retrieved 1 mdm(s)
MDM-ID 39f317742b58aa0f SDC ID 749f21e000000005 INSTALLATION ID 5082d8992e46577b IPs [0]-192.168.18.103 [1]-192.168.18.104
Verifying the feature gates.
fail: 0
NAME: vxflexos
LAST DEPLOYED: Sun Jun 23 17:19:59 2019
NAMESPACE: vxflexos
STATUS: DEPLOYED
RESOURCES:
==> v1/ClusterRole
NAME AGE
vxflexos-controller 4s
vxflexos-node 4s
==> v1/ClusterRoleBinding
NAME AGE
vxflexos-controller 4s
vxflexos-node 4s
==> v1/Pod(related)
NAME READY STATUS RESTARTS AGE
vxflexos-controller-0 0/4 ContainerCreating 0 4s
vxflexos-node-8g2zb 0/2 ContainerCreating 0 4s
vxflexos-node-swfsl 0/2 ContainerCreating 0 4s
==> v1/ServiceAccount
NAME SECRETS AGE
vxflexos-controller 1 4s
vxflexos-node 1 4s
==> v1/StorageClass
NAME PROVISIONER AGE
vxflexos (default) csi-vxflexos 4s
vxflexos-xfs csi-vxflexos 4s
==> v1alpha1/CSIDriver
NAME AGE
vxflexos 4s
==> v1beta1/StatefulSet
NAME READY AGE
vxflexos-controller 0/1 4s
==> v1beta2/DaemonSet
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
vxflexos-node 2 2 0 2 0 4s
NAME READY STATUS RESTARTS AGE
vxflexos-controller-0 0/4 ContainerCreating 0 10s
vxflexos-node-8g2zb 0/2 ContainerCreating 0 10s
vxflexos-node-swfsl 0/2 ContainerCreating 0 10s
NAME READY STATUS RESTARTS AGE
vxflexos-controller-0 0/4 ContainerCreating 0 15s
vxflexos-node-8g2zb 0/2 ContainerCreating 0 15s
vxflexos-node-swfsl 0/2 ContainerCreating 0 15s
NAME READY STATUS RESTARTS AGE
vxflexos-controller-0 0/4 ContainerCreating 0 20s
vxflexos-node-8g2zb 0/2 ContainerCreating 0 20s
vxflexos-node-swfsl 0/2 ContainerCreating 0 20s
CSIDrivers:
NAME AGE
vxflexos 20s
CSINodeInfos:
No resources found.
StorageClasses:
NAME PROVISIONER AGE
vxflexos (default) csi-vxflexos 20s
vxflexos-xfs csi-vxflexos 20s
error: the server doesn't have a resource type "volumesnapshotclass"
installing volumesnapshotclass
error: unable to recognize "volumesnapshotclass.yaml": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1alpha1"
VolumeSnapshotClasses:
error: the server doesn't have a resource type "volumesnapshotclass"
- 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
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 20mBack 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
2 Intern
•
10 Posts
4333
0
Posted 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