search

operator-framework / operator-lifecycle-manager

A management framework for extending Kubernetes with Operators
https://olm.operatorframework.io
Apache License 2.0
1.72k stars 545 forks source link

OLM not work in a specific name space #2870

Open vincent-pli opened 2 years ago

vincent-pli commented 2 years ago

Bug Report

What did you do? Try to install operator with operator hub to a specific NS, the namespace is create several months ago and alreay have some operator running.

What did you expect to see? Deployment of operator start to run

What did you see instead? Under which circumstances? Nothing happened, there is only a subscription. its state is normal. No related installplan or CVS generated. The state of catalogsources is ok.

Then I check the log of catalog-operator, nothing wrong but one thing is dubiously:

time="2022-09-28T23:31:53Z" level=warning msg="an error was encountered during reconciliation" error="Operation cannot be fulfilled on subscriptions.operators.coreos.com \"ibm-user-data-services-operator\": StorageError: invalid object, Code: 4, Key: /kubernetes.io/operators.coreos.com/subscriptions/ibm-common-services/ibm-user-data-services-operator, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 01268747-7774-4821-b304-87f84bb92aa3, UID in object meta: " event=update reconciling="*v1alpha1.Subscription" selflink=

But when I install same operator in another NS, everything works as expected.

That's weird, that's means catalogsources works well, the OLM works well. but not work with a specific NS. Any clue will be welcome, thanks

Environment

Possible Solution

Additional context Add any other context about the problem here.

awgreene commented 2 years ago

Seems related to https://github.com/kubernetes/kubernetes/issues/82130.

If the subscription isn't tied to an operator, I would recommend deleting and recreating it as a workaround.