Skip to content

pre-existing CRD owners found for owned CRD(s) of dependent CSV #2722

@kaovilai

Description

@kaovilai

Bug Report

Related to #1347 but clusterServiceVersionNames field is populated.

What did you do?
A clear and concise description of the steps you took (or insert a code snippet).
Refresh catalogsource
What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).
UpgradeSuccessful
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: 0.18.3
  • Kubernetes version information:
kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5+5c84e52", GitCommit:"ce18cbe56f6e88a8fc0e06366afe113b415ad39b", GitTreeState:"clean", BuildDate:"2022-03-01T18:44:38Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
  • Kubernetes cluster kind: OpenShift 4.9

Possible Solution

Additional context
Add any other context about the problem here.

CatalogSource creation and updates was automated by Github actions attached in Gist. Also attached installed and installing installplans.
gist

Note that I am opening this issue as "FYI/still exist today" since this is dev environment and I have since worked around the issue by simply uninstalling previous operator first and reinstalling.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions