This repository has been archived by the owner on Jun 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 91
Operator cannot be updated using OLM #1026
Labels
kind/bug
Something isn't working
Comments
wtrocki
changed the title
[Critical] Operator cannot be updated using OLM
Operator cannot be updated using OLM
Sep 17, 2021
If you notice that problem. Workaround: Remove both operators |
Error message:
The reason is most likely the change of the name of the /cc @pedjak |
@pmacik Thank you so much! |
Is this issue fixed now?
And I uninstall 0.9.1 and reinstall 0.10.0 is succeed. |
This is an OLM issue, reported here: operator-framework/operator-lifecycle-manager#1608 and closed with a proposed workaround, that we cannot apply on the existing releases. Closing. Moving forward we will have that proposed workaround in mind. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the environment (Minikube, Openshift)?
New version fails to update on the number of clusters (tests, end users, demo clusters, workshops etc.).
What is the SBO version used?
0.10.0
What are the steps to reproduce this issue?
What is the expected behaviour?
Operator running
What is the actual behaviour?
Operator ends up in some strange state (two operators visible)
New one crashing in the loop (logs attached)
Old is not functional
Service Binding Operator Logs
Logs:
https://gist.github.com/b1zzu/c33f01cc1d565adcab2165295cf38f02
Additional Information (Screenshots, etc)
The text was updated successfully, but these errors were encountered: