Files

T

Blaine Gardner fc56108865 object: allow status endpoints to be null

For the upgrade case, Rook can fail to set status information
on CephObjectStores after CRDs are updated but before the operator is
updated. To fix this, merely allow the slices to be null in the
CephObjectStore's status.endpoints.

This PR seems to be aggravating the helm filesystem upgrade test. Allow
30 more seconds for CRDs to be done before bailing. In debugging, the
filesystem often needed only an extra 3 seconds to succeed.

Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>

2022-11-08 13:36:15 -07:00

framework

object: allow status endpoints to be null

2022-11-08 13:36:15 -07:00

integration

object: do not create service for external object stores

2022-11-04 17:30:30 -06:00

manifests

ci: use stringData instead of data for secret

2022-04-25 16:41:27 +02:00

scripts

nfs: fix nfs grace period when multus is enabled

2022-10-05 16:28:36 -06:00

.gitignore

tests: refactor integration tests

2017-06-29 15:20:28 -07:00

ceph-status-out

core: change directory layout

2021-11-30 09:12:53 +01:00

README.md

docs: fixed the developer guide link in README.md

2022-08-16 14:30:00 +05:30

README.md

Rook Test Framework

The Rook Test Framework is used to run end to end and integration tests on Rook. The framework depends on a running instance of Kubernetes. The framework also provides scripts for starting Kubernetes so users can quickly spin up a Kubernetes cluster. The Test framework is designed to install Rook, run tests, and uninstall Rook.

Install Kubernetes

To install Kubernetes follow Rook's developer guide.

Run Tests

1. Build rook

Now that the Kubernetes cluster is running we need to populate the Docker registry environment variables:

eval $(minikube docker-env -p minikube)

The build process will build and push the images to the Docker registry inside the Minikube virtual machine.

make build

Now tag the newly built images to rook/ceph:local-build for running tests, or rook/ceph:master if creating sample manifests::

docker tag $(docker images|awk '/build-/ {print $1}') rook/ceph:local-build
docker tag rook/ceph:local-build rook/ceph:master

2. Run integration tests

Some settings are available to run the tests under different environments. The settings are all configured with environment variables. See environment.go for the available environment variables. At least you should set the following variables.

export TEST_HELM_PATH=/tmp/rook-tests-scripts-helm/linux-amd64/helm
export TEST_BASE_DIR=WORKING_DIR
export TEST_SCRATCH_DEVICE=/dev/vdb

Change the TEST_SCRATCH_DEVICE and point it to the correct block device name based on the driver that's being used. If you are using the virtualbox minikube driver, the device should be /dev/sdb.

Please note that the integration tests erase the contents of TEST_SCRATCH_DEVICE.

To run all integration tests:

go test -v -timeout 7200s github.com/rook/rook/tests/integration

After running tests, you can get test logs under tests/integration/_output.

To run a specific suite (uses regex):

go test -v -timeout 1800s -run CephSmokeSuite github.com/rook/rook/tests/integration

To run specific tests inside a suite:

go test -v -timeout 1800s -run CephSmokeSuite github.com/rook/rook/tests/integration -testify.m TestARookClusterInstallation_SmokeTest

3. To run tests on OpenShift environment

Setup OpenShift environment and export KUBECONFIG before executing the tests.
Make sure oc executable file is in the PATH.
Only CephSmokeSuite is currently supported on OpenShift.
Set few environment variables:

export TEST_ENV_NAME=openshift
export TEST_STORAGE_CLASS=gp2
export TEST_BASE_DIR=/tmp
export RETRY_MAX=40

To run the CephSmokeSuite:

go test -v -timeout 1800s -run CephSmokeSuite github.com/rook/rook/tests/integration