-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
It is not possible to test automatically che-operator updates #16738
Comments
Launched on OCP4.4 and I've obtain the same errors. Hower launching the same scripts on OCP4.3 seems is working without any problem. Installing in OCP 4.4 also I received this event:
|
do we know if the problem is 4.4 itself (different behaviour) or network issues? |
I want to mention I test update from 7.11.0 to 7.12.0 on minikube(1.8.2 version) and seems is working. I change OLM version from 0.12.0 to 0.14.0. |
@tolusha setting P1, but please update the labels based on the team priorities |
An error hasn't been reproduced on latest OCP 4.4-rc.11 cluster. |
If this is resolved, please update #16690 (comment) when you have news about the PRs being done. |
Fixed olm version to test operator updates on minikube. |
Describe the bug
To check updates we use the test script [1]
It fails with such an error
The reason being is that
operator-source
is removed from latest version of olm.[1] https://github.com/eclipse/che-operator/blob/master/olm/testUpdate.sh
Environment
The text was updated successfully, but these errors were encountered: