[FLINK-31180] Fail early when installing minikube and check whether we can retry

• Type: Improvement
• Status: Closed
• Priority: Not a Priority
• Resolution: Duplicate
• Affects Version/s: 1.17.0, 1.15.3, 1.16.1
• Component/s: Test Infrastructure
• Labels: auto-deprioritized-minor pull-request-available starter test-stability
• Assignee: Unassigned
• Reporter: Matthias Pohl
• Created: 22/Feb/23 07:43
• Updated: 23/Oct/23 08:49
• Resolved: 23/Oct/23 08:49

Description

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=46367&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&t=b2642e3a-5b86-574d-4c8a-f7e2842bfb14&l=4726

We experienced a build failure where Minikube couldn't be installed due to some network issues. Two things which we could do here:

• check whether we can add a retry loop (maybe also to other resource)
• fail early if CI didn't manage to install the binaries

Issue Links

• links to: GitHub Pull Request #23497