-
Notifications
You must be signed in to change notification settings - Fork 545
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
e2e - "should create a Subscription for the latest entry providing the required GVK" failure #2600
Comments
I looked at this farther. I saw the same error in the catalog-operator log but I couldn't reproduce this error locally. The resolve finished successfully after many reconciliations. In the CI catalog-operator log, I saw the error of the
In the log of local test has this:
It says 'i/o timeout' |
The first test (this test) started at 20:00:17.685407819Z
and finished at 20:01:34.043344211Z
I see the
So most of time during the first test, the operatorhubio-catalog was not in the READY state. It probably affected the test. |
This failure has the same cause. https://github.com/operator-framework/operator-lifecycle-manager/runs/4961201219?check_suite_focus=true#step:4:206 The catalog-operator log has this:
|
I haven't read all the comments in this issue, but generally speaking, I think it's fine if we want to make it a testing requirement that we wait until the CatalogSource testing fixture is reporting a Ready state before we run any test cases. The only caveats would be any tests where we want to test the non-happy paths. |
Bug Report
e2e - "should create a Subscription for the latest entry providing the required GVK" failed.
https://github.com/operator-framework/operator-lifecycle-manager/runs/4957261384?check_suite_focus=true#step:4:154
What did you do?
Check CI e2e test failure
What did you expect to see?
No error
What did you see instead? Under which circumstances?
error above
Environment
Possible Solution
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: