operator-framework
An InstallPlan corresponds to two different operator Subscriptions.
Bug Report
What did you do?
Install both operators in the same namespace, and then check the ownerReferences of the InstallPlan where the operator was installed first.
What did you expect to see?
Each installplan corresponds correctly to a Subscription.
What did you see instead? Under which circumstances? A clear and concise description of what you expected to happen (or insert a code snippet).
Environment
- operator-lifecycle-manager version:
quay.m.daocloud.io/operator-framework/olm:v0.25.0
- Kubernetes version information:
[root@demo-dev-master1 ~]# kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.4", GitCommit:"872a965c6c6526caa949f0c6ac028ef7aff3fb78", GitTreeState:"clean", BuildDate:"2022-11-09T13:36:36Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.4", GitCommit:"872a965c6c6526caa949f0c6ac028ef7aff3fb78", GitTreeState:"clean", BuildDate:"2022-11-09T13:29:58Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"linux/amd64"}
[root@demo-dev-master1 ~]#
- Kubernetes cluster kind:
normal kubernetes
Possible Solution
Additional context Add any other context about the problem here.
This bug report is confusing. Is the second screenshot after you edited something? The first screenshot should have had the spec of the installPlan.
I got an install plan which had two different operators in the clusterServiceVersionNames and also in the status and ownerReferences.
Using olm 0.26.0.
The additional CSV was from an update for another operator that I haven't approved.
In the spec for the subscription I had just added I had specified installPlanApproval as automatic, while the additional outstanding update was set to Manual.
