ceph-csi/e2e
Niels de Vos a04a0ecc9f ci: retry command in Pod on "unable to upgrade connection" error
Sometimes executing a command in a Pod fails with "unable to upgrade
connection". This is most likely a temporary situation, and retrying
hopefully reduces the number of spurious failures because of it.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-07-29 16:39:26 +00:00
..
templates e2e: add deployment example for ROX used by multiple pods mounting same device 2021-11-23 13:13:41 +00:00
ceph_user.go e2e: add Copyright header of e2e files 2021-12-23 03:47:00 +00:00
cephfs_helper.go e2e: add test case for snapshot metadata validation 2022-07-28 19:37:23 +00:00
cephfs.go e2e: CephFS validate restore and clone metadata 2022-07-28 19:37:23 +00:00
clone.go ci: fix all linter errors found in golangci-lint 2022-06-03 12:55:54 +00:00
configmap.go ci: fix all linter errors found in golangci-lint 2022-06-03 12:55:54 +00:00
deploy-vault.go e2e: add Copyright header of e2e files 2021-12-23 03:47:00 +00:00
deployment.go e2e: add tests to validate cluster name 2022-06-08 16:23:59 +00:00
e2e_test.go e2e: add -nfs-driver=... option to select provisioner 2022-05-10 00:43:43 +00:00
errors_test.go e2e: add isAlreadyExistsCLIError to check known error 2021-08-06 08:03:18 +00:00
errors.go ci: retry command in Pod on "unable to upgrade connection" error 2022-07-29 16:39:26 +00:00
kms.go e2e: correct the cephfs fuse verification podnames 2022-04-11 12:15:48 +00:00
log.go cleanup: resolve nlreturn linter issues 2021-07-22 06:05:01 +00:00
migration.go e2e: make recreateCSIRBDPods() function to a generic one 2022-01-04 13:48:36 +00:00
namespace.go cleanup: use os.ReadFile to read file 2022-01-24 05:25:11 +00:00
nfs.go e2e: remove kubernetes 1.22 check 2022-07-25 07:35:41 +00:00
node.go e2e: add Copyright header of e2e files 2021-12-23 03:47:00 +00:00
pod.go ci: retry command in Pod on "unable to upgrade connection" error 2022-07-29 16:39:26 +00:00
pvc.go e2e: pass non-empty Namespace/Name in deletePVCAndPV() 2022-06-30 00:27:27 +00:00
rbd_helper.go rebase: update csi-snapshotter to v6 2022-06-16 18:45:33 +00:00
rbd.go e2e: remove kubernetes 1.22 check 2022-07-25 07:35:41 +00:00
README.md e2e: remove snapshot beta CRD mention from the doc 2022-05-26 13:43:17 +00:00
resize.go e2e: add getPersistentVolumeClaim helper function 2022-05-06 15:55:54 +00:00
snapshot.go rebase: update csi-snapshotter to v6 2022-06-16 18:45:33 +00:00
staticpvc.go ci: fix all linter errors found in golangci-lint 2022-06-03 12:55:54 +00:00
upgrade-cephfs.go e2e: add getPersistentVolumeClaim helper function 2022-05-06 15:55:54 +00:00
upgrade-rbd.go e2e: add getPersistentVolumeClaim helper function 2022-05-06 15:55:54 +00:00
upgrade.go e2e: add Copyright header of e2e files 2021-12-23 03:47:00 +00:00
utils.go e2e: add deadcode nolint for k8sVersionGreaterEquals 2022-07-25 07:35:41 +00:00

End-to-End Testing

Introduction

End-to-end (e2e) in cephcsi provides a mechanism to test the end-to-end behavior of the system, These tests will interact with live instances of ceph cluster just like how a user would.

The primary objectives of the e2e tests are to ensure a consistent and reliable behavior of the cephcsi code base and to catch hard-to-test bugs before users do when unit and integration tests are insufficient.

The Test framework is designed to install Rook, run cephcsi tests, and uninstall Rook.

The e2e test are built on top of Ginkgo and Gomega

Install Kubernetes

The cephcsi also provides a script for starting Kubernetes using minikube so users can quickly spin up a Kubernetes cluster.

the following parameters are available to configure kubernetes cluster

flag description
up Starts a local kubernetes cluster and prepare a disk for rook
down Stops a running local kubernetes cluster
clean Deletes a local kubernetes cluster
ssh Log into or run a command on a minikube machine with SSH
deploy-rook Deploy rook to minikube
create-block-pool Creates a rook block pool (named $ROOK_BLOCK_POOL_NAME)
delete-block-pool Deletes a rook block pool (named $ROOK_BLOCK_POOL_NAME)
clean-rook Deletes a rook from minikube
cephcsi Copy built docker images to kubernetes cluster
k8s-sidecar Copy kubernetes sidecar docker images to kubernetes cluster

following environment variables can be exported to customize kubernetes deployment

ENV Description Default
MINIKUBE_VERSION minikube version to install latest
KUBE_VERSION kubernetes version to install latest
MEMORY Amount of RAM allocated to the minikube VM in MB 4096
VM_DRIVER VM driver to create virtual machine virtualbox
CEPHCSI_IMAGE_REPO Repo URL to pull cephcsi images quay.io/cephcsi
K8S_IMAGE_REPO Repo URL to pull kubernetes sidecar images registry.k8s.io/sig-storage
K8S_FEATURE_GATES Feature gates to enable on kubernetes cluster BlockVolume=true,CSIBlockVolume=true,VolumeSnapshotDataSource=true
ROOK_BLOCK_POOL_NAME Block pool name to create in the rook instance newrbdpool
  • creating kubernetes cluster

    From the ceph-csi root directory, run:

    ./scripts/minikube.sh up
    
  • Teardown kubernetes cluster

    ./scripts/minikube.sh clean
    

Deploy Rook

The cephcsi E2E tests expects that you already have rook running in your cluster.

Thanks to minikube script for the handy deploy-rook option.

./scripts/minikube.sh deploy-rook

Test parameters

In addition to standard go tests parameters, the following custom parameters are available while running tests:

flag description
deploy-timeout Timeout to wait for created kubernetes resources (default: 10 minutes)
deploy-cephfs Deploy cephFS CSI driver as part of E2E (default: true)
deploy-rbd Deploy rbd CSI driver as part of E2E (default: true)
test-cephfs Test cephFS CSI driver as part of E2E (default: true)
upgrade-testing Perform upgrade testing (default: false)
upgrade-version Target version for upgrade testing (default: "v3.5.1")
test-rbd Test rbd CSI driver as part of E2E (default: true)
cephcsi-namespace The namespace in which cephcsi driver will be created (default: "default")
rook-namespace The namespace in which rook operator is installed (default: "rook-ceph")
kubeconfig Path to kubeconfig containing embedded authinfo (default: $HOME/.kube/config)
timeout Panic test binary after duration d (default 0, timeout disabled)
v Verbose: print additional output
is-openshift Run in OpenShift compatibility mode, skips certain new feature tests
filesystem Name of the CephFS filesystem (default: "myfs")
clusterid Use the Ceph cluster id in the StorageClasses and SnapshotClasses (default: ceph fsid detected)
nfs-driver Name of the driver to use for provisioning NFS-volumes (default: "nfs.csi.ceph.com")

E2E for snapshot

After the support for snapshot/clone has been added to ceph-csi, you need to follow these steps before running e2e.

  • Install snapshot controller and snapshot CRD

    ./scripts/install-snapshot.sh install
    

    Once you are done running e2e please perform the cleanup by running following:

    ./scripts/install-snapshot.sh cleanup
    

Running E2E

Note:- Prior to running the tests, you may need to copy the kubernetes configuration file to$HOME/.kube/configwhich is required to communicate with kubernetes cluster or you can passkubeconfigflag while running tests.

Functional tests are run by the go test command.

go test ./e2e/ -timeout=20m -v -mod=vendor

To run specific tests, you can specify options

go test ./e2e/ --test-cephfs=false --test-rbd=false --upgrade-testing=true

To run e2e for specific tests with make, use

make run-e2e E2E_ARGS="--test-cephfs=false --test-rbd=true --upgrade-testing=false"

You can also invoke functional tests with make command

make func-test TESTOPTIONS="-deploy-timeout=10 -timeout=30m -v"