NO-JIRA: Create an openshift/conformance/ocp-flaky test suite

[deads2k]

Nearly all of our tests are reliable enough to not need a retry. Let's eliminate the retry and make flaky tests obvious. The new periodic jobs we create based on this test will still show up in component readiness and sippy results.

[openshift-ci-robot]

@deads2k: This pull request explicitly references no jira issue.

In response to this:

Nearly all of our tests are reliable enough to not need a retry. Let's eliminate the retry and make flaky tests obvious. The new periodic jobs we create based on this test will still show up in component readiness and sippy results.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [deads2k]

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

[openshift-ci]

@deads2k: 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/prow/e2e-hypershift-conformance	94c6286	link	false	/test e2e-hypershift-conformance
ci/prow/e2e-metal-ipi-ovn	94c6286	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-gcp-csi	94c6286	link	false	/test e2e-gcp-csi
ci/prow/e2e-openstack-ovn	94c6286	link	false	/test e2e-openstack-ovn
ci/prow/e2e-agnostic-ovn-cmd	94c6286	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/okd-scos-e2e-aws-ovn	94c6286	link	false	/test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.