Log what monitortests failed in Stop() leading to the failed resultState

[dgoodwin]

No description provided.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

• 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]

@dgoodwin: 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-metal-ipi-ovn-ipv6	3432027	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-metal-ipi-ovn	3432027	link	false	/test e2e-metal-ipi-ovn
ci/prow/verify	3432027	link	true	/test verify
ci/prow/e2e-aws-ovn-edge-zones	3432027	link	true	/test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-csi	3432027	link	false	/test e2e-aws-csi
ci/prow/e2e-gcp-ovn	3432027	link	true	/test e2e-gcp-ovn
ci/prow/unit	3432027	link	true	/test unit
ci/prow/e2e-aws-ovn-single-node-upgrade	3432027	link	false	/test e2e-aws-ovn-single-node-upgrade

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.

[stbenjam]

/payload-job periodic-ci-openshift-hypershift-release-4.17-periodics-e2e-aws-ovn-conformance

[openshift-ci]

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

• periodic-ci-openshift-hypershift-release-4.17-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5d6d43d0-21af-11ef-9de2-d89de992f721-0

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale