OCPERT-151: add oap testdata to hotfix for test panic: Asset test/extended/testdata/oap/mustgather not found

[ming1013]

After https://github.com/openshift/openshift-tests-private/pull/26954 merged, test will meet Test Panicked: Asset test/extended/testdata/oap/mustgather not found.
The solution is working on https://issues.redhat.com/browse/OCPERT-169.
And this is a hotfix to add test data of oap to do a quickly resolve.

[openshift-ci-robot]

@ming1013: This pull request references OCPERT-151 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:

After https://github.com/openshift/openshift-tests-private/pull/26954 merged, test will meet Test Panicked: Asset test/extended/testdata/oap/mustgather not found.
The solution is working on https://issues.redhat.com/browse/OCPERT-169.
And this is a hotfix to add test data of oap to do a quickly resolve.

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.

[ming1013]

/request-review @rioliu-rh

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ming1013
Once this PR has been reviewed and has the lgtm label, please assign keenonlee 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:

• test/extended/util/compat_otp/testdata/OWNERS

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

[ming1013]

/hold The solution in https://github.com/openshift/openshift-tests-private/pull/27518 seems start taking effect, if it works, then no need to update origin testdata

[openshift-ci]

@ming1013: 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-rt-upgrade	dc7e736	link	false	/test e2e-gcp-ovn-rt-upgrade
ci/prow/okd-scos-e2e-aws-ovn	dc7e736	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-cgroupsv2	dc7e736	link	false	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-gcp-csi	dc7e736	link	false	/test e2e-gcp-csi
ci/prow/images	dc7e736	link	true	/test images
ci/prow/e2e-metal-ipi-ovn	dc7e736	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-fips	dc7e736	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-single-node-upgrade	dc7e736	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	dc7e736	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-microshift	dc7e736	link	true	/test e2e-aws-ovn-microshift
ci/prow/e2e-vsphere-ovn	dc7e736	link	true	/test e2e-vsphere-ovn
ci/prow/e2e-aws-ovn-serial-1of2	dc7e736	link	true	/test e2e-aws-ovn-serial-1of2
ci/prow/e2e-aws-ovn-single-node-serial	dc7e736	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-edge-zones	dc7e736	link	false	/test e2e-aws-ovn-edge-zones
ci/prow/e2e-agnostic-ovn-cmd	dc7e736	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-metal-ipi-ovn-ipv6	dc7e736	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-gcp-ovn-upgrade	dc7e736	link	true	/test e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-serial-2of2	dc7e736	link	true	/test e2e-aws-ovn-serial-2of2
ci/prow/e2e-aws-ovn-microshift-serial	dc7e736	link	true	/test e2e-aws-ovn-microshift-serial
ci/prow/e2e-aws-ovn-single-node	dc7e736	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-csi	dc7e736	link	false	/test e2e-aws-csi
ci/prow/e2e-gcp-ovn	dc7e736	link	true	/test e2e-gcp-ovn
ci/prow/e2e-openstack-ovn	dc7e736	link	false	/test e2e-openstack-ovn
ci/prow/e2e-vsphere-ovn-upi	dc7e736	link	true	/test e2e-vsphere-ovn-upi

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.