Exclude new backends to avoid failing in aggregated jobs

[DennisPeriquet]

TRT-1095

The new backends are enumerated in the backend_disruption...json file and not present in the older backend_disruption...json files like this.

To get the list of new ones, I did this and compared current one with one before the new backends were added.

$ cat backend-disruption_20230619-190241.json |jq '.BackendDisruptions|keys[]'

Reference: the new backends were added in these functions.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[dgoodwin]

/lgtm

/override ci/prow/e2e

This is broken on the repo I think.

[openshift-ci]

@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e

In response to this:

/lgtm

/override ci/prow/e2e

This is broken on the repo I think.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DennisPeriquet, dgoodwin

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:

• pkg/jobrunaggregator/OWNERS [dgoodwin]

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

[openshift-ci]

@DennisPeriquet: all tests passed!

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