Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import managed cluster failed cause by version conflict on OKD #42

Open
xuezhaojun opened this issue Jun 2, 2021 · 2 comments
Open
Labels

Comments

@xuezhaojun
Copy link
Member

After processed these steps:

Step1 : Install community operator from OperatorHub.io
Step2 : Create a Cluster Manager on console
Step3 : Install the managedcluster-import-controller from source files
Step4 : Manually register a cluster

We got error:

E0526 05:51:18.661381       1 lease_controller.go:127] unable to get cluster lease "managed-cluster-lease" on hub cluster: leases.coordination.k8s.io "managed-cluster-lease" is forbidden: User "system:open-cluster-management:cluster1:cv6xm" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "cluster1"

We fixed it by change all images version in the import.yaml from "latest" to "0.0.3" at Step4

@skeeey
Copy link
Member

skeeey commented Jun 3, 2021

This because hub is 0.0.3 (2.2), but add-on is latest (2.3), we cannot support to use a low version hub to work with high version add-on (the low version add-on can be worked with high version hub)

@qiujian16
Copy link
Member

/kind bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants