Fix robustness test logs by identifing failpoint availability on temporary cluster before creating subtest

[serathius]

cc @ahrtr @fuweid @henrybear327 @siyuanfoundation @MadhavJivrajani

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 68.76%. Comparing base (2b32307) to head (cd1aa92). Report is 954 commits behind head on main.

Additional details and impacted files

see 19 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #18685      +/-   ##
==========================================
- Coverage   68.78%   68.76%   -0.02%     
==========================================
  Files         420      420              
  Lines       35629    35629              
==========================================
- Hits        24506    24500       -6     
- Misses       9700     9702       +2     
- Partials     1423     1427       +4     

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 2b32307...cd1aa92. Read the comment docs.

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fuweid, serathius, siyuanfoundation

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~~ [serathius]

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

[fuweid]

/retest

[serathius]

This fails in CI for some reason. Need to debug more.

[k8s-ci-robot]

PR needs rebase.

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.

[github-actions[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

[k8s-ci-robot]

@serathius: 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
pull-etcd-integration-1-cpu-amd64	cd1aa92b24cf1289cd10757a982d8d9f55e5a0d9	link	true	/test pull-etcd-integration-1-cpu-amd64
pull-etcd-robustness-arm64	cd1aa92b24cf1289cd10757a982d8d9f55e5a0d9	link	true	/test pull-etcd-robustness-arm64
pull-etcd-robustness-amd64	cd1aa92b24cf1289cd10757a982d8d9f55e5a0d9	link	true	/test pull-etcd-robustness-amd64
ci-etcd-robustness-release34-amd64	cd1aa92b24cf1289cd10757a982d8d9f55e5a0d9	link	true	/test ci-etcd-robustness-release34-amd64
ci-etcd-robustness-release36-amd64	cd1aa92b24cf1289cd10757a982d8d9f55e5a0d9	link	true	/test ci-etcd-robustness-release36-amd64
ci-etcd-robustness-release35-amd64	cd1aa92b24cf1289cd10757a982d8d9f55e5a0d9	link	true	/test ci-etcd-robustness-release35-amd64

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.