Skip to content

Make sure TPNU or CustomNoUpgrade FG does not affect test results #20701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
openshift-merge-robot merged 1 commit into from
Jul 29, 2021
Merged

Make sure TPNU or CustomNoUpgrade FG does not affect test results #20701

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions ...r/step-registry/openshift/e2e/aws/ccm/install/openshift-e2e-aws-ccm-install-workflow.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,5 +13,9 @@ workflow:
- chain: ipi-aws-post
env:
TEST_CSI_DRIVER_MANIFEST: manifest-aws-ebs.yaml
TEST_SKIPS: >-
Managed cluster should start all core operators\|
Alerts shouldn't report any alerts in firing or pending state\|
Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured
documentation: |-
The Openshift E2E AWS CCM install workflow executes the common end-to-end test suite on AWS with a cluster configuration including CCM pods
4 changes: 4 additions & 0 deletions ...ep-registry/openshift/e2e/azure/ccm/install/openshift-e2e-azure-ccm-install-workflow.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,5 +12,9 @@ workflow:
- chain: ipi-azure-post
env:
TEST_CSI_DRIVER_MANIFEST: manifest-aws-ebs.yaml
TEST_SKIPS: >-
Managed cluster should start all core operators\|
Alerts shouldn't report any alerts in firing or pending state\|
Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured
documentation: |-
The Openshift E2E Azure CCM install workflow executes the common end-to-end test suite on Azure with a cluster configuration including CCM pods
4 changes: 4 additions & 0 deletions ci-operator/step-registry/openshift/e2e/azure/ccm/openshift-e2e-azure-ccm-workflow.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,10 @@ workflow:
CLUSTERCSIDRIVER: disk.csi.azure.com
TRUECONDITIONS: AzureDiskDriverControllerServiceControllerAvailable AzureDiskDriverNodeServiceControllerAvailable
TEST_CSI_DRIVER_MANIFEST: manifest-azure-disk.yaml
TEST_SKIPS: >-
Managed cluster should start all core operators\|
Alerts shouldn't report any alerts in firing or pending state\|
Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured
documentation: |-
The Openshift E2E Azure workflow using CCM as a primary mean to initialize nodes.
Executes the common end-to-end test suite on Azure to test updated cluster configuration.
4 changes: 4 additions & 0 deletions ...rator/step-registry/openshift/e2e/openstack/ccm/openshift-e2e-openstack-ccm-workflow.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,10 @@ workflow:
env:
CONFIG_TYPE: "minimal"
BASE_DOMAIN: shiftstack.devcluster.openshift.com
TEST_SKIPS: >-
Managed cluster should start all core operators\|
Alerts shouldn't report any alerts in firing or pending state\|
Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured
documentation: |-
The openshift-e2e-openstack-ipi workflow executes the common
end-to-end test suite on OpenShift ipi intallation on OpenStack
Expand Down