Description
Bug Report
What did you do?
We're seeing an issue where we:
- create a catalog source and operator group
- install and then uninstall the operator
- delete the catalog source and operator group
The above all works fine.
Next, we:
- immediately create a new catalog (same everything except the contained CSV has a different supported install mode)
- create a new operator group supporting the new install mode.
- create a subscription to ask OLM to install the operator
What did you expect to see?
Successful installation of the operator with tweaked install mode without changing anything else in the CSV from the initial installation.
What did you see instead? Under which circumstances?
It seems OLM is caching package data and not invalidating it when the catalog source data changes.
Rather than seeing a successful installation, I pretty quickly see that the CSV immediately fails with an error that the operator group that exists does not support the CSV's supported install mode, but I know that they CSV supported install modes and the new operator group align and should work.
Environment
- operator-lifecycle-manager version:
0.16.1
- Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.8", GitCommit:"9f2892aab98fe339f3bd70e3c470144299398ace", GitTreeState:"clean", BuildDate:"2020-08-13T16:12:48Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:48:36Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
- Kubernetes cluster kind:
minikube
Possible Solution
Additional context
Add any other context about the problem here.