search

operator-framework / operator-lifecycle-manager

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

On reinstalling Open Data Hub operator in a project, it gets stuck on Upgrade pending #2674

Open richaiter08 opened 2 years ago

richaiter08 commented 2 years ago

Bug Report

OpenDataHub_Not Getting Instlled

What did you do? A clear and concise description of the steps you took (or insert a code snippet).

What did you expect to see? A clear and concise description of what you expected to happen (or insert a code snippet).

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

Possible Solution

Additional context Add any other context about the problem here.

exdx commented 2 years ago

Could you provide any additional information on the cluster state? Checking the subscription or the installplan status may provide clues as to why the installation is stuck in pending. You could also check the logs of the OLM operator to see if there is something more readily apparent there.

richaiter08 commented 2 years ago

Could you provide any additional information on the cluster state? Checking the subscription or the installplan status may provide clues as to why the installation is stuck in pending. You could also check the logs of the OLM operator to see if there is something more readily apparent there

I did check the logs. But didnt seem to find any detail present. As of now I have had to retire the machine. But I am still facing issues in setting up ODH in other clusters. It is now giving an error of "Failed: csv created in namespace with multiple operatorgroups, can't pick one automatically" Even on deleting the operator and reinstalling, we keep getting the same error and other operators are failing as well

exdx commented 2 years ago

Hi @richaiter08,

Thanks for getting back with that info. Having more than one OperatorGroup in a namespace is a terminal error, you can read more about it here: https://olm.operatorframework.io/docs/concepts/crds/operatorgroup/#toomanyoperatorgroups

I would recommend moving all OperatorGroups in the namespace, and then creating a new one with a blank spec so all installmodes are supported -- you should potentially see your installation succeed afterwards.