[FLINK-30355] crictl causes long wait in e2e tests

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.17.0
• Fix Version/s: 1.17.0
• Component/s: Test Infrastructure, Tests
• Labels: pull-request-available test-stability
• Assignee: Martijn Visser
• Reporter: Matthias Pohl
• Created: 09/Dec/22 16:04
• Updated: 19/Dec/22 13:47
• Resolved: 19/Dec/22 13:47

Description

We observed strange behavior in the e2e test where the e2e test run times out: https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=43824&view=logs&j=bea52777-eaf8-5663-8482-18fbc3630e81&s=ae4f8708-9994-57d3-c2d7-b892156e7812&t=b2642e3a-5b86-574d-4c8a-f7e2842bfb14&l=7446

The issue seems to be related to crictl again because we see the following error message in multiple tests. No logs are produced afterwards for ~30mins resulting in the overall test run taking too long:

Dec 09 08:55:39 crictl
fatal: destination path 'cri-dockerd' already exists and is not an empty directory.
fatal: a branch named 'v0.2.3' already exists
mkdir: cannot create directory ‘bin’: File exists
Dec 09 09:26:41 fs.protected_regular = 0

Issue Links

• links to: GitHub Pull Request #21520