search

kubevirt / hyperconverged-cluster-operator

Operator pattern for managing multi-operator products
Apache License 2.0
154 stars 152 forks source link

SSP operator does not install the SSP webhook #356

Closed rmohr closed 4 years ago

rmohr commented 4 years ago

I get 

E1118 09:45:16.429192       1 reflector.go:134] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:196: Failed to list *unstructured.Unstructured: clusterroles.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:kubevirt-hyperconverged:kubevirt-ssp-operator" cannot list resource "clusterroles" in API group "rbac.authorization.k8s.io" at the cluster scope

in the SSP opoerator logs and I see after make cluster-up && make cluster-sync only the SSP operator:

kubevirt-hyperconverged   bridge-marker-wjbbt                                   1/1     Running   0          10m
kubevirt-hyperconverged   cdi-apiserver-6fc5dc58c7-wsh8d                        1/1     Running   0          10m
kubevirt-hyperconverged   cdi-deployment-d959c59db-hhvhk                        1/1     Running   0          10m
kubevirt-hyperconverged   cdi-operator-6fbd7df95-vkv86                          1/1     Running   0          13m
kubevirt-hyperconverged   cdi-uploadproxy-5594d48c97-vkrk2                      1/1     Running   0          10m
kubevirt-hyperconverged   cluster-network-addons-operator-66678c696f-pbvcf      1/1     Running   0          13m
kubevirt-hyperconverged   hyperconverged-cluster-operator-64445b57f8-bqtkl      1/1     Running   0          13m
kubevirt-hyperconverged   kube-cni-linux-bridge-plugin-gsng4                    1/1     Running   0          10m
kubevirt-hyperconverged   kube-multus-ds-amd64-q725c                            1/1     Running   0          10m
kubevirt-hyperconverged   kubemacpool-mac-controller-manager-54765764d4-8kzqm   1/1     Running   0          10m
kubevirt-hyperconverged   kubemacpool-mac-controller-manager-54765764d4-qtcsv   1/1     Running   0          10m
kubevirt-hyperconverged   kubevirt-ssp-operator-55f68f4b85-7m879                1/1     Running   0          13m
kubevirt-hyperconverged   nmstate-handler-rsqtv                                 1/1     Running   0          10m
kubevirt-hyperconverged   node-maintenance-operator-78d8b664-jq9pg              1/1     Running   0          13m
kubevirt-hyperconverged   ovs-cni-amd64-gp6h9                                   2/2     Running   0          10m
kubevirt-hyperconverged   virt-api-5b84d5457c-ts9l9                             1/1     Running   0          10m
kubevirt-hyperconverged   virt-api-5b84d5457c-wcf8j                             1/1     Running   0          10m
kubevirt-hyperconverged   virt-controller-c898c7675-m89hl                       1/1     Running   0          8m11s
kubevirt-hyperconverged   virt-controller-c898c7675-zndql                       1/1     Running   0          8m11s
kubevirt-hyperconverged   virt-handler-g8dvz                                    1/1     Running   0          8m11s
kubevirt-hyperconverged   virt-operator-54d57dd946-njttq                        1/1     Running   0          13m
kubevirt-hyperconverged   virt-operator-54d57dd946-wmqjg                        1/1     Running   0          13m
rmohr commented 4 years ago

/kind bug

rmohr commented 4 years ago

/assign @rthallisey

kubevirt-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot commented 4 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

rmohr commented 4 years ago

@tiraboschi I guess this was fixed in the meantime?

kubevirt-bot commented 4 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 4 years ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/hyperconverged-cluster-operator/issues/356#issuecomment-615214846): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.