verbose / debug mode?
Opened this issue · 1 comments
reefland commented
I had a notice about CSIDriver Object
missing, but not sure what its looking for that could be missing, below that it says This is a CSI driver
.
Explore your Kubernetes storage options
**************************************
Kubernetes Version Check:
Valid kubernetes version (v1.28.6+k3s2) - OK
RBAC Check:
Kubernetes RBAC is enabled - OK
Aggregated Layer Check:
The Kubernetes Aggregated Layer is enabled - OK
Available Storage Provisioners:
rook-ceph.rbd.csi.ceph.com:
Missing CSIDriver Object. Required by some provisioners.
This is a CSI driver!
(The following info may not be up to date. Please check with the provider for more information.)
Provider: Ceph RBD
Website: https://github.com/ceph/ceph-csi
Description: A Container Storage Interface (CSI) Driver for Ceph RBD
Additional Features: Raw Block, Snapshot, Expansion, Topology, Cloning
Storage Classes:
* ceph-block
* csi-ceph-block
Volume Snapshot Classes:
* ceph-block
* csi-ceph-blockpool
To perform a FIO test, run-
./kubestr fio -s <storage class>
To perform a check for block device support, run-
./kubestr blockmount -s <storage class>
To test CSI snapshot/restore functionality, run-
./kubestr csicheck -s <storage class> -v <volume snapshot class>
All the test pass except this one, but seems to get past the snapshot.
$ ./kubestr csicheck -s csi-ceph-block -v csi-ceph-blockpool
Creating application
-> Created pod (kubestr-csi-original-pod5qrp7) and pvc (kubestr-csi-original-pvc8jj4k)
Taking a snapshot
-> Created snapshot (kubestr-snapshot-20240306111352)
Restoring application
-> Restored pod (kubestr-csi-cloned-podvk896) and pvc (kubestr-csi-cloned-pvc77rcv)
Cleaning up resources
CSI checker test:
Failed to fetch data from pod. Failure may be due to permissions issues. Try again with runAsUser=1000 option.: Failed to exec command in pod: command terminated with exit code 1 - Error
Error: Failed to fetch data from pod. Failure may be due to permissions issues. Try again with runAsUser=1000 option.: Failed to exec command in pod: command terminated with exit code 1
Since it cleaned up all resources, I have nothing to look at to troubleshoot and don't see a way to get more verbose or debug information from the test. Suggestions? Thanks
reefland commented
Resolved test issue. But request for verbose / debug mode would be handy.
$ ./kubestr csicheck -s csi-ceph-block -v csi-ceph-blockpool
Creating application
-> Created pod (kubestr-csi-original-podd6czf) and pvc (kubestr-csi-original-pvc5ql6x)
Taking a snapshot
-> Created snapshot (kubestr-snapshot-20240306132739)
Restoring application
-> Restored pod (kubestr-csi-cloned-podzccg5) and pvc (kubestr-csi-cloned-pvc4f8rs)
Cleaning up resources
CSI checker test:
CSI application successfully snapshotted and restored. - OK