OpenShift: Strimzi Operator stuck at version 0.45.1

[lukasertl]

On our OpenShift cluster I had successfully updated Strimzi operator by changing the update channel in the subscription from strimzi-0.a.x to strimzi-0.b.x over several versions.

I'm now at update channel strimzi-0.45.x and the operator updated to strimzi-0.45.1.

Now, if I change the subscription to strimzi-0.46.x nothing happens; the change is completely ignored, no errors, no warnings.

I ran a few tests and found that if I manually update to strimzi-0.45.0 and ignore the .1 release, I can update further to 0.46.

Is there any known bug with 0.45.1 that would lead me to a dead end in the update path?

[im-konge]

I guess it's not issue with the version, rather the path for replaces in OLM -> as we had 0.45.0 and then 0.46.0, then we added 0.45.1 to the 0.45.x channel and 0.46.1 to the 0.46.x channel - which breaks the upgrade path (and the replaces field). The way how OLM works and how it is configured in the community operators is that you would need to update the whole replaces path for all previous versions (which would mean replacing everything from 0.45.0 to for example 0.48.0 as the latest current release), which - as you can see - is complicated thing.

What you can do is to have 0.45.1 installed and once you would like to upgrade to something newer, delete the operator (without deleting the operands etc - this is important) and then install a new one with the version you want. That's what is IIRC also recommended in OLM itself.

[lukasertl]

That makes sense and is really helpful - I was able to delete the operator version 0.45.1 and install higher version without problems.

Thanks a lot!

[im-konge]

No problem, glad it helped.