Closed harshshekhar15 closed 4 years ago
CSI-operators in 2.0.0 will only be deployed on k8s clusters having version >1.17.0. The cluster on which the above testcase is getting deployed is on k8s version v1.15.11 so the csi-operators are not getting deployed due to which volume was not getting provisioned.
Ref - https://mayadata-team.slack.com/archives/CJK9753QC/p1598885637037100
We'll be upgrading k8s clusters in Rancher pipeline to v1.18.
This issue was resolved after upgrading the C3 cluster to v1.18.6. Ref - https://github.com/mayadata-io/oep-e2e/issues/871
Successful job post upgrade - TCID-DIR-OP-DELETE-CSPC-WITH-VOLUME
Issue
TCID-DIR-OP-DELETE-CSPC-WITH-VOLUME testcase is failing in Rancher with the following error message -
Status code was 201 and not [405]
.Gitlab pipeline job details - TCID-DIR-OP-DELETE-CSPC-WITH-VOLUME
Testcase details
This is a negative testcase in which we deploy minio consuming a raidz type cstor pool and we try to delete that pool which should not get deleted ideally. But in this case it is getting deleted.
Issue details
The pool is getting deleted here so the status code is 201 and not 405. It is getting deleted because the minio pod is in
Pending
state and on describing it shows the below -pod has unbound immediate PersistentVolumeClaims (repeated 5 times)
. On investigating further we found out that the pvc created for minio was also inPending
state and on describing it showed -waiting for a volume to be created, either by external provisioner "cstor.csi.openebs.io" or manually created by system administrator
.Pipeline details
Kubera version - 2.0.0-RC1.ee Cluster - Cluster3 Testcase - TCID-DIR-OP-DELETE-CSPC-WITH-VOLUME K8s version - v1.15.11