olm: Add dedicated prowjob for running flaky e2e tests

[timflannagan]

Introduces a new prowjob for running the flaky OLM e2e tests in parallel with the OLM e2e suite. This new prowjob has an optional status requirement.

[timflannagan]

Note: this is just a stopgap until openshift/operator-framework-olm#264 lands in the downstream OLM repository, which includes the upstream commit for segmenting flaky tests into their own github actions. We can look into consolidating this into a single target where the default behavior is to skip the flaky tests to avoid having to make changes to multiple repositories when we make a chance to any of the root/staging Makefiles.

[timflannagan]

/test e2e-aws-olm-flaky

[openshift-ci]

@timflannagan: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test app-ci-config-dry
• /test boskos-config
• /test boskos-config-generation
• /test build-clusters
• /test build01-dry
• /test build02-dry
• /test build03-dry
• /test build04-dry
• /test ci-operator-config
• /test ci-operator-config-metadata
• /test ci-operator-registry
• /test ci-secret-bootstrap-config-validation
• /test ci-testgrid-allow-list
• /test config
• /test core-valid
• /test correctly-sharded-config
• /test deprecate-templates
• /test generated-config
• /test generated-dashboards
• /test hive-dry
• /test openshift-image-mirror-mappings
• /test ordered-prow-config
• /test owners
• /test pj-rehearse-blocking
• /test prow-config
• /test prow-config-filenames
• /test prow-config-semantics
• /test pylint
• /test release-config
• /test release-controller-config
• /test secret-generator-config-valid
• /test services-valid
• /test step-registry-metadata
• /test step-registry-shellcheck
• /test sync-rover-groups
• /test yamllint

The following commands are available to trigger optional jobs:

• /test arm01-dry
• /test pj-rehearse
• /test pj-rehearse-max
• /test pj-rehearse-more
• /test vsphere-dry

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-release-master-build-clusters
• pull-ci-openshift-release-master-ci-operator-config
• pull-ci-openshift-release-master-ci-operator-config-metadata
• pull-ci-openshift-release-master-ci-operator-registry
• pull-ci-openshift-release-master-config
• pull-ci-openshift-release-master-core-valid
• pull-ci-openshift-release-master-correctly-sharded-config
• pull-ci-openshift-release-master-deprecate-templates
• pull-ci-openshift-release-master-generated-config
• pull-ci-openshift-release-master-ordered-prow-config
• pull-ci-openshift-release-master-owners
• pull-ci-openshift-release-master-pj-rehearse
• pull-ci-openshift-release-master-prow-config-filenames
• pull-ci-openshift-release-master-prow-config-semantics
• pull-ci-openshift-release-openshift-image-mirror-mappings
• pull-ci-openshift-release-yamllint

Details

In response to this:

/test e2e-aws-olm-flaky

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[timflannagan]

/retest

[timflannagan]

The e2e-aws-olm-flaky test correctly ran zero test specs:

�[1m�[32mRan 0 of 178 Specs in 1.416 seconds�[0m

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_release/26973/rehearse-26973-pull-ci-openshift-operator-framework-olm-master-e2e-aws-olm-flaky/1503536401482780672/artifacts/e2e-aws-olm-flaky/test/build-log.txt

[perdasilva]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva, timflannagan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/operator-framework-olm/OWNERS [perdasilva,timflannagan]
• ci-operator/jobs/openshift/operator-framework-olm/OWNERS [perdasilva,timflannagan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@timflannagan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/rehearse/openshift/operator-framework-olm/master/e2e-aws-olm	5c7a59e	link	unknown	/test pj-rehearse
ci/rehearse/openshift/operator-framework-olm/release-4.12/e2e-aws-olm	5c7a59e	link	unknown	/test pj-rehearse
ci/prow/pj-rehearse	5c7a59e	link	false	/test pj-rehearse

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-ci]

@timflannagan: Updated the following 4 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-operator-framework-olm-master.yaml using file ci-operator/config/openshift/operator-framework-olm/openshift-operator-framework-olm-master.yaml
• ci-operator-4.12-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-operator-framework-olm-release-4.12.yaml using file ci-operator/config/openshift/operator-framework-olm/openshift-operator-framework-olm-release-4.12.yaml
• job-config-master-presubmits configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-operator-framework-olm-master-presubmits.yaml using file ci-operator/jobs/openshift/operator-framework-olm/openshift-operator-framework-olm-master-presubmits.yaml
• job-config-4.12 configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-operator-framework-olm-release-4.12-presubmits.yaml using file ci-operator/jobs/openshift/operator-framework-olm/openshift-operator-framework-olm-release-4.12-presubmits.yaml

Details

In response to this:

Introduces a new prowjob for running the flaky OLM e2e tests in parallel with the OLM e2e suite. This new prowjob has an optional status requirement.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.