some enhancement for e2e-analysis

[jianlinliu]

1. Per slack discussion, we are going to add one more test case - "ensure 1 worker node at least gets ready", once the case fails, it will skip the following operators health check.
2. Always create junit directory if it does not exist

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@jianlinliu: This pull request references TRT-2275 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.21.0" version, but no target version was set.

In response to this:

Per slack discussion, we are going to add one more test case - "ensure 1 worker node at least gets ready", once the case fails, it will skip the following operators health check.

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

@jianlinliu: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

Per slack discussion, we are going to add one more test case - "ensure 1 worker node at least gets ready", once the case fails, it will skip the following operators health check.

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]

@jianlinliu: 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-gcp-ovn-techpreview-serial-2of2	60f2a81	link	false	/test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-metal-ipi-ovn-dualstack	60f2a81	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-disruptive	60f2a81	link	false	/test e2e-aws-disruptive
ci/prow/e2e-azure	60f2a81	link	false	/test e2e-azure
ci/prow/e2e-gcp-ovn-techpreview	60f2a81	link	false	/test e2e-gcp-ovn-techpreview
ci/prow/e2e-aws-ovn-microshift	7d2bcc8	link	true	/test e2e-aws-ovn-microshift
ci/prow/e2e-openstack-ovn	7d2bcc8	link	false	/test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node	7d2bcc8	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-edge-zones	7d2bcc8	link	false	/test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-ovn-serial-1of2	7d2bcc8	link	true	/test e2e-aws-ovn-serial-1of2
ci/prow/e2e-aws-ovn-microshift-serial	7d2bcc8	link	true	/test e2e-aws-ovn-microshift-serial
ci/prow/e2e-metal-ipi-ovn	7d2bcc8	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-fips	7d2bcc8	link	true	/test e2e-aws-ovn-fips
ci/prow/okd-scos-e2e-aws-ovn	7d2bcc8	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade	7d2bcc8	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-csi	7d2bcc8	link	false	/test e2e-aws-csi
ci/prow/e2e-metal-ipi-ovn-ipv6	7d2bcc8	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-single-node-serial	7d2bcc8	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-agnostic-ovn-cmd	7d2bcc8	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-cgroupsv2	7d2bcc8	link	false	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	7d2bcc8	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout

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.