MCO-1828: Fix pathological tests for disruptive suite

[pablintino]

This commit adds a behavior change to the way matchers work to allow some matchers to apply during "disruptive periods" in disruptive runs. During disruptive periods (delimited by start-end matchers) a new type of matcher can target a given set of events to "skip" its occurence.

[openshift-ci-robot]

@pablintino: This pull request references MCO-1828 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

This commit adds a behavior change to the way matchers work to allow some matchers to apply during "disruptive periods" in disruptive runs. During disruptive periods (delimited by start-end matchers) a new type of matcher can target a given set of events to "skip" its occurence.

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 NOT APPROVED

This pull-request has been approved by: pablintino
Once this PR has been reviewed and has the lgtm label, please assign dennisperiquet for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

@pablintino: 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-openstack-ovn	ab9854e	link	false	/test e2e-openstack-ovn
ci/prow/e2e-metal-ipi-serial-2of2	ab9854e	link	false	/test e2e-metal-ipi-serial-2of2
ci/prow/e2e-aws-ovn-microshift	ab9854e	link	true	/test e2e-aws-ovn-microshift
ci/prow/e2e-aws-disruptive	ab9854e	link	false	/test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	ab9854e	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-upgrade	ab9854e	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-fips	ab9854e	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-gcp-ovn-techpreview	ab9854e	link	false	/test e2e-gcp-ovn-techpreview
ci/prow/e2e-gcp-ovn	ab9854e	link	true	/test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2	ab9854e	link	false	/test e2e-metal-ipi-serial-ovn-ipv6-2of2

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.

[pablintino]

/payload-job periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-aws-mco-disruptive-techpreview

[openshift-ci]

@pablintino: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-machine-config-operator-release-4.20-periodics-e2e-aws-mco-disruptive-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4b527690-833b-11f0-9461-d621147b248f-0