Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3292

Loki Controller manager in CrashLoop due to failure to list *v1.Proxy

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Log Storage - Sprint 227

      Loki Controller manager is in crashloop state after multiple restarts. service account cannot list resource "proxies" in API group "config.openshift.io" at the cluster scope

      Controller Logs:

      W1115 00:25:47.504726 1 reflector.go:424] pkg/mod/k8s.io/client-go@v0.25.2/tools/cache/reflector.go:169: failed to list *v1.Proxy: proxies.config.openshift.io is forbidden: User "system:serviceaccount:openshift-operators-redhat:default" cannot list resource "proxies" in API group "config.openshift.io" at the cluster scope
      E1115 00:25:47.504772 1 reflector.go:140] pkg/mod/k8s.io/client-go@v0.25.2/tools/cache/reflector.go:169: Failed to watch *v1.Proxy: failed to list *v1.Proxy: proxies.config.openshift.io is forbidden: User "system:serviceaccount:openshift-operators-redhat:default" cannot list resource "proxies" in API group "config.openshift.io" at the cluster scope

      Steps to reproduce:
      1) Deploy Loki Operator on Logging 5.6
      2) Check controller logs

      How reproducible: Always

      Version: loki-operator.v5.6.0  

      Expected Result: Controller should be up and running with no errors

      Actual Result: Controller is in crash loop status

            [LOG-3292] Loki Controller manager in CrashLoop due to failure to list *v1.Proxy

            Kabir Bharti added a comment - - edited

            Verified on loki-operator.v5.6.0 using ocp4-index:latest. Controller is now running without errors.

            [kbharti@cube hack]$ oc get pods -n openshift-operators-redhat
            NAME                                                READY   STATUS    RESTARTS   AGE
            elasticsearch-operator-8844c6746-mjg8c              2/2     Running   0          32m
            loki-operator-controller-manager-84b6949bd4-kfqk8   2/2     Running   0          25m
            

            Kabir Bharti added a comment - - edited Verified on loki-operator.v5.6.0 using ocp4-index:latest. Controller is now running without errors. [kbharti@cube hack]$ oc get pods -n openshift-operators-redhat NAME                                                READY   STATUS    RESTARTS   AGE elasticsearch- operator -8844c6746-mjg8c              2/2     Running   0          32m loki- operator -controller-manager-84b6949bd4-kfqk8   2/2     Running   0          25m

              ptsiraki@redhat.com Periklis Tsirakidis
              rhn-support-kbharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: