The Openshift E2E oVirt `csi` release 4.6,4.7 workflow installs OpenShift cluster on top of oVirt
from releases that didn't contain affinity groups and secure connection to the oVirt engine from the installer,
therefor it uses a different install config and ovirt-config.
Executes the `openshift/csi` end-to-end test suite.
Volume resizing tests are disabled, releases 4.6,4.7 doesn't support volume resizing.
This step saves existing storage objects (PVs, StorageClasses, CSIDrivers)
after cluster installation. These objects are used by storage-obj-check step
to tell which of them existed before e2e tests started and which are
leftovers of the e2e tests.
This step compares existing storage objects (PVs, StorageClasses, CSIDrivers)
in the cluster with objects saved in storage-obj-save step to ensure that e2e
tests don't leave any stray objects behind and all volumes are deleted.
If the test suite requires SSH access, setting this variable will install a bastion and configure the Kube e2e test infrastructure to use the bastion. Otherwise, tests that require SSH will fail because OpenShift does not expose SSH to nodes by default.
Regular expression (POSIX basic regular expression) of tests to skip.
It is suggested to test the regex to make sure that it matches with the available tests.
Tests can be listed by using 'openshift-tests run --dry-run (...)'. Sometimes, the tests
that are printed in Prow won't exactly match the list returned by openshift-tests.
The type of test to perform.
* 'suite' - Run the test suite defined by TEST_SUITE. By default this executes the
OpenShift parallel conformance suite. All product components must run the
default suite on pull requests prior to merge.
* 'suite-conformance' - Runs the test suite defined by TEST_SUITE, then runs the product conformance
suite to verify the cluster is still functional. This is typically used for testing
disruption from one suite, then confirming that the disruption did not degrade the
* 'upgrade' - Perform an upgrade to the image defined by OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE.
The TEST_UPGRADE_OPTIONS flag may be optionally set. All product components
must run the default upgrade test (verify an upgrade completes) on pull requests
prior to merge.
* 'upgrade-conformance' - Performs the 'upgrade' test and then executes the full conformance
suite after upgrade completes. Does not honor TEST_SUITE but will respect
TEST_UPGRADE_OPTIONS. All product releases must pass the conformance suite after
an upgrade completes or have explicit logic in their test to tolerate behavior after
* 'upgrade-paused' - Perform an upgrade to the images defined by OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE with paused worker pool.