Workflow: openshift-upgrade-ovirt-release-4.4-4.5

The Openshift E2E oVirt upgrade release 4.4,4.5 workflow installs OpenShift cluster on top of oVirt from releases that didn't contain the oVirt csi driver, therefor patch the image registry. Executes an upgrade to the next available version.

Pre Steps

Name Description
ipi-ovirt-pre-upgrade-release-4.4-4.5 The IPI setup step contains all steps that provision an OpenShift cluster on oVirt and no PVC (release 4.4 and 4.5 don't have CSI on oVirt).
ipi-install-ovirt-patch-image-registry On 4.4 and 4.5 we don't have CSI Driver so we need to patch that image registry to use emptydir.

Test Steps

Name Description
openshift-e2e-test The Openshift E2E step executes the common end-to-end test suite.

Post Steps

Name Description
ipi-ovirt-post The IPI cleanup step contains all steps that deprovision an OpenShift cluster on oVirt, provisioned by the `ipi-ovirt-pre` chain.

Dependencies

Image Exposed As Override[?] Required By Steps
release:initial OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE yes ipi-install-install-stableinitial
release:latest OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE yes openshift-e2e-test
RELEASE_IMAGE_LATEST no ipi-install-install-stableinitial

Environment

In addition to the default environment, the following variables are consumed through this workflow

Variable Name Variable Content Consumed By Steps
ARM64_RELEASE_OVERRIDE Hack to pass the release override for ARM64 tests. ipi-install-install-stableinitial
OPENSHIFT_INSTALL_EXPERIMENTAL_DUAL_STACK Using experimental Azure dual-stack support (default: false) ipi-install-install-stableinitial
TEST_ARGS Additional arguments to be passed to 'openshift-test' openshift-e2e-test
TEST_CSI_DRIVER_MANIFEST Name of the CSI driver manifest file to use. Used by the `openshift-tests` program as TEST_CSI_DRIVER_FILES env. var., see its documentation for details. The file must be present in ${SHARED_DIR}. openshift-e2e-test
TEST_INSTALL_CSI_DRIVERS The CSI driver(s) to use. Used by the `openshift-tests` program, see its documentation for details. openshift-e2e-test
TEST_REQUIRES_SSH 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. openshift-e2e-test
TEST_SKIPS 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. openshift-e2e-test
TEST_SUITE The test suite to run. Use 'openshift-test run --help' to list available suites. (default: openshift/conformance/parallel) openshift-e2e-test
TEST_TYPE 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 product. * '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. * 'upgrade-paused' - Perform an upgrade to the images defined by OPENSHIFT_UPGRADE_RELEASE_IMAGE_OVERRIDE with paused worker pool. (default: suite) openshift-e2e-test
TEST_UPGRADE_OPTIONS Options controlling how an upgrade is performed. See `openshift-test run-upgrade --help` for more details. openshift-e2e-test
TEST_UPGRADE_SUITE The test suite to run in upgrade tests. Use 'openshift-test run --help' to list available suites. (default: all) openshift-e2e-test

Step Graph

Webreg Workflow "openshift-upgrade-ovirt-release-4.4-4.5" cluster_3 Pre cluster_2 ipi-ovirt-pre-upgrade-release-4.4-4.5 cluster_0 ipi-conf-ovirt-release-4.4-4.5 cluster_1 ipi-install-ovirt-stableinitial cluster_4 Test cluster_8 Post cluster_7 ipi-ovirt-post cluster_6 ipi-deprovision cluster_5 gather 0 ipi-conf-ovirt-generate-install-config-params 1 ipi-conf-ovirt-generate-ovirt-config-insecure 0->1 2 ipi-conf-ovirt-generate-install-config-release-4.4-4.5 1->2 3 ipi-install-rbac 2->3 4 ipi-install-ovirt-send-event-to-ovirt-pre 3->4 5 ipi-install-install-stableinitial 4->5 6 ipi-install-ovirt-send-event-to-ovirt-post 5->6 7 ipi-install-ovirt-patch-image-registry 6->7 8 openshift-e2e-test 7->8 9 gather-core-dump 8->9 10 gather-must-gather 9->10 11 gather-extra 10->11 12 gather-audit-logs 11->12 13 ipi-deprovision-deprovision 12->13

GitHub Link:

https://github.com/openshift/release/blob/master/ci-operator/step-registry/openshift/upgrade/ovirt/release-4.4-4.5/openshift-upgrade-ovirt-release-4.4-4.5-workflow.yaml

Owners:

Approvers:

Reviewers:

Source code for this page located on GitHub