-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test flake in test/cmd/images.sh #6259
Comments
This is an image import problem (or just a dockerhub unavailability problem, but at the end of the day the failure is that the imagestream did not import despite being created, whatever the reason). Routing to @pweil- to delegate. |
Similar issue here:
|
@stevekuznetsov volunteered and @soltysh is doing a rebase so, I'll reassign for now. |
We never see the
The sever gets the shutdown signal milliseconds after the Also, we do not clean up well enough, it looks like. A build from |
sounds like it's worth bumping it then, make it 2 minutes. that should future proof us for a while, anyway. |
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/7886/
|
The image import controller is hanging attempting to import tags from the internal registry, which is not running in test-cmd.sh (no node or registry is running). The controller attempts twice, each time taking 30 seconds to time out. Detailed logs at The failed test is in the cmd-newapp namespace:
server logs referencing image streams start around
Image import controller is still busy with other namespaces. You can see 30-second periods of inactivity followed by an i/o timeout trying to hit the internal registry (which is not running):
Image import controller finally starts importing from the cmd-newapp image streams almost a full minute after they are created, but by then it is too late:
|
If the reason for the flakes is that we hit a 30s timeout twice only because of the way the test environment is set up here, do we need to do anything other than changing the wait time? Is the logic for re-trying the import sound? |
changing the wait time is not the right solution. I would like to do the following things:
|
There seem to be a lot of problems with this sort of behavior - the logs for |
I'll parallelize and operate against live data after the cheap check |
Looks like we sometimes import the stream but not the tag? flake on getting an image stream tag here:
|
Increasing priority due to prevalence: https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/bfa-proj-graphs/detailedgraphs (scroll down) |
The new flakes (caused by docker hub timing out) are covered in other issues, closing this |
!!! Error in test/cmd/../../hack/cmd_util.sh:409
'return 1' exited with status 1
Call stack:
1: test/cmd/../../hack/cmd_util.sh:409 os::cmd::try_until_success(...)
2: test/cmd/images.sh:49 main(...)
Exiting with status 1
!!! Error in hack/test-cmd.sh:284
https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/4284/console
The text was updated successfully, but these errors were encountered: