You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have seen this flake a few times, it is unclear why it is happening.
In all of the cases the error is provided port is already allocated
In the following two cases the error is on the below line.
The text was updated successfully, but these errors were encountered:
AustinAbro321
changed the title
"provided port is already allocated" test flake can occassionally happen during e2e cross cluster tests
CI flake: "provided port is already allocated" occassionally happens during e2e cross cluster tests
Mar 5, 2024
We believe that during the first two occurrences of the the problem was the registry port 31337 assigned in the test conflicted with the randomly generated trafeik ports created by k3d. This will be solved by disabling trafeik during e2e tests in #2282.
The third issue is an actual bug in zarf. It is caused by the fact that the injector (seed registry) selects a random port and this port could conflict with the registry port. Looking at the logs here confirms this as the seed registry matches the registry in the logs https://github.com/defenseunicorns/zarf/actions/runs/8012041029/job/21886586280.
Yeah it's only like a 1 in 3000 chance, but it's still worth fixing for the init case. Especially since this can also happen to real uses if they have the proper luck or lack thereof
We have seen this flake a few times, it is unclear why it is happening.
In all of the cases the error is
provided port is already allocated
In the following two cases the error is on the below line.
We also see a similar error here on here on test 99:
The text was updated successfully, but these errors were encountered: