Skip to content
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

ROSA e2e tests timeout consistently #554

Open
rhmdnd opened this issue Jul 22, 2024 · 0 comments
Open

ROSA e2e tests timeout consistently #554

rhmdnd opened this issue Jul 22, 2024 · 0 comments

Comments

@rhmdnd
Copy link

rhmdnd commented Jul 22, 2024

There appears to be a transient issue in the ROSA e2e tests that gives the following error:

024/07/22 20:04:55 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:00 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:05 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:10 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:15 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:20 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:25 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:30 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:35 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:40 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:45 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:50 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:05:55 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:06:00 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:06:05 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:06:10 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:06:15 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:06:20 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:06:20 Waiting for full availability of compliance-operator deployment (0/1)
2024/07/22 20:06:20 timed out waiting for deployment to become available: timed out waiting for the condition
FAIL	github.com/ComplianceAsCode/compliance-operator/tests/e2e/rosa	1802.787s
FAIL
make: *** [Makefile:616: e2e-rosa] Error 1
{"component":"entrypoint","error":"wrapped process failed: exit status 2","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-07-22T20:06:20Z"}
error: failed to execute wrapped command: exit status 2 
INFO[2024-07-22T20:06:21Z] Step e2e-rosa-test-ocp4-pci-dss-node failed after 31m10s. 
INFO[2024-07-22T20:06:21Z] Step phase test failed after 31m10s.         
INFO[2024-07-22T20:06:21Z] Running multi-stage phase post               

Unclear what is causing this, but opening a ticket since it's prevalent across almost all patches and causing a lot of rechecks.

#546 is an example where we're rechecking quite a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant