Workflow: openshift-upgrade-openstack-loki

The Openshift E2E openstack workflow executes the upgrade end-to-end test suite on openstack with a default cluster configuration and loki as log collector, exercising an upgrade during the process.

Pre Steps

Name Description
ipi-install-hosted-loki The IPI install loki step deploys logging solution for collecting container logs and sending those to Loki hosted on Grafana Cloud.
ipi-openstack-pre-stableinitial The ipi-openstack-pre-stableinitial chain contains the necessary refs and chains to prepare the system to run ipi install on OpenStack from release:initial imagestream
ipi-conf-openstack-enable-octavia The ipi-conf-openstack-enable-octavia amends cloud config to enable Octavia LB support

Test Steps

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

Post Steps

Name Description
ipi-openstack-post The ipi-openstack-post chain inludes all the refs and chains necessary to tear down an ipi installation of OpenShift on Openstack.


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


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

Variable Name Variable Content Consumed By Steps
ADDITIONAL_WORKERS_NETWORKS Space-separated list of Neutron network names that will be connected to the worker nodes. openstack-conf-generateconfig
ALLOCATION_POOL_END (default: openstack-provision-machinesubnet
ALLOCATION_POOL_START (default: openstack-provision-machinesubnet
API_VIP (default: openstack-provision-machinesubnet
APPLICATION_CREDENTIALS If this variable is not empty, the provided clouds.yaml will contain ephemeral application credentials. openstack-conf-clouds
APPLICATION_CREDENTIALS_EXPIRATION When to set the expiration of the application credentials. Use a format that `date -d` would understand. This variable has no effect if APPLICATION_CREDENTIALS is empty. (default: 5 hours) openstack-conf-clouds
ARM64_RELEASE_OVERRIDE Hack to pass the release override for ARM64 tests. ipi-install-install-stableinitial
BASE_DOMAIN openstack-conf-generateconfig openstack-conf-creatednsrecords ipi-conf-openstack-precheck openstack-deprovision-deletednsrecords
BASTION_FLAVOR The flavor of the bastion machine. Defaults to the value in "${SHARED_DIR}/BASTION_FLAVOR" openstack-provision-bastionproxy
BASTION_IMAGE The image of the bastion machine (default: centos8-stream) openstack-provision-bastionproxy
BASTION_SUBNET_RANGE (default: openstack-provision-machinesubnet
BASTION_USER The user of the bastion machine (default: centos) openstack-provision-bastionproxy openstack-deprovision-bastionproxy
CLUSTER_TYPE_OVERRIDE This will override CLUSTER_TYPE in the `commands` file if set. openstack-conf-clouds openstack-conf-resourcenames
CONFIG_TYPE The type of config for the environment to deploy. * 'minimal' - Configure the install-config with the minimal options to make it work on our tests, which requires the usage of floating IPs. This config type doesn't require a proxy server to be deployed. * 'byon' - Configure the install-config to use a pre-created network (BYON) so it wouln't require the usage of floating IPs. This config type will require a proxy server to be deployed. * 'proxy' - Configure the install-config to use a pre-created restricted network (BYON) and a Cluster Proxy. openstack-provision-machinesubnet openstack-provision-bastionproxy openstack-conf-createfips openstack-conf-generateconfig openstack-conf-generateconfig openstack-conf-creatednsrecords openstack-deprovision-bastionproxy openstack-deprovision-machinesubnet
DNS_IP (default: openstack-provision-machinesubnet
FIPS_ENABLED (default: false) openstack-conf-generateconfig
INGRESS_VIP (default: openstack-provision-machinesubnet
NETWORK_TYPE The Network type used during the installation (default: OpenShiftSDN) openstack-provision-bastionproxy openstack-conf-generateconfig
OPENSHIFT_INSTALL_EXPERIMENTAL_DUAL_STACK Using experimental Azure dual-stack support (default: false) ipi-install-install-stableinitial
OPENSTACK_COMPUTE_FLAVOR If not passed, the command script chooses the value based on CLUSTER_TYPE. openstack-conf-resourcenames openstack-conf-generateconfig
OPENSTACK_CONTROLPLANE_FLAVOR If not passed, the command script chooses the value based on CLUSTER_TYPE. openstack-conf-resourcenames openstack-conf-generateconfig
OPENSTACK_EXTERNAL_NETWORK If not passed, the command script chooses the value based on CLUSTER_TYPE. openstack-conf-resourcenames openstack-provision-machinesubnet openstack-provision-bastionproxy openstack-conf-createfips openstack-conf-generateconfig
OPENSTACK_PROVIDER_NETWORK Name of the OpenStack provider network if any. openstack-provision-machinesubnet openstack-conf-generateconfig openstack-deprovision-machinesubnet
OS_CLOUD name of cloud to use from clouds.yaml (default: openstack) openstack-gather openstack-conf-clouds openstack-provision-machinesubnet openstack-provision-bastionproxy openstack-provision-proxyconf openstack-conf-createfips openstack-conf-generateconfig openstack-conf-exportcindercredentials openstack-deprovision-bastionproxy openstack-deprovision-deletefips openstack-deprovision-machinesubnet
SUBNET_RANGE (default: openstack-provision-machinesubnet
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
TRY_COUNT number of times to retry (default: 5) ipi-conf-openstack-precheck
WAIT_TIME number of seconds to wait before trying. (default: 60) ipi-conf-openstack-precheck
ZONES If not passed, the command script chooses the value based on CLUSTER_TYPE. openstack-conf-resourcenames openstack-conf-generateconfig
ZONES_COUNT The number of AZs to present in the cluster. Accepted values are 0 and 1. (default: 0) openstack-provision-machinesubnet openstack-provision-bastionproxy openstack-conf-generateconfig

Step Graph

Webreg Workflow "openshift-upgrade-openstack-loki" cluster_3 Pre cluster_2 ipi-openstack-pre-stableinitial cluster_0 ipi-conf-openstack-noramfs cluster_1 ipi-install-stableinitial cluster_4 Test cluster_9 Post cluster_8 ipi-openstack-post cluster_6 ipi-deprovision cluster_5 gather cluster_7 ipi-deprovision-openstack 0 ipi-install-hosted-loki 1 openstack-conf-clouds 0->1 2 openstack-conf-resourcenames 1->2 3 openstack-provision-machinesubnet 2->3 4 openstack-provision-bastionproxy 3->4 5 openstack-provision-proxyconf 4->5 6 openstack-conf-createfips 5->6 7 openstack-conf-generateconfig 6->7 8 openstack-conf-creatednsrecords 7->8 9 openstack-conf-exportcindercredentials 8->9 10 ipi-conf-openstack-precheck 9->10 11 ipi-install-monitoringpvc 10->11 12 ipi-install-rbac 11->12 13 ipi-install-install-stableinitial 12->13 14 ipi-conf-openstack-enable-octavia 13->14 15 openshift-e2e-test 14->15 16 openstack-gather 15->16 17 gather-must-gather 16->17 18 gather-extra 17->18 19 gather-audit-logs 18->19 20 ipi-deprovision-deprovision 19->20 21 openstack-deprovision-deletednsrecords 20->21 22 openstack-deprovision-bastionproxy 21->22 23 openstack-deprovision-deletefips 22->23 24 openstack-deprovision-machinesubnet 23->24

GitHub Link:




Source code for this page located on GitHub