Cluster not found error about weave-gitops

[Cajga]

I see the same in our deployment. Values for helm:

    envVars:
      - name: WEAVE_GITOPS_FEATURE_OIDC_BUTTON_LABEL
        value: "Login with AzureAD"
      - name: WEAVE_GITOPS_FEATURE_TENANCY
        value: "true"
      - name: WEAVE_GITOPS_FEATURE_CLUSTER
        value: "false"
    additionalArgs:
      - --auth-methods=oidc

Errors from weave-gitops pod when we are browsing:

2023-09-19T11:37:10.144Z	INFO	gitops	middleware/middleware.go:65	server error	{"uri": "/v1/object/rester-helm-dev?namespace=rester-helm-dev&kind=GitRepository", "status": 500}
2023-09-19T11:37:10.155Z	ERROR	gitops	middleware/middleware.go:39	server error	{"error": "cluster= not found"}
2023-09-19T11:37:10.155Z	INFO	gitops	middleware/middleware.go:65	server error	{"uri": "/v1/object/flux-system?namespace=flux-system&kind=GitRepository", "status": 500}
2023-09-19T11:37:10.160Z	ERROR	gitops	middleware/middleware.go:39	server error	{"error": "cluster= not found"}
2023-09-19T11:37:10.160Z	INFO	gitops	middleware/middleware.go:65	server error	{"uri": "/v1/object/rester-plain-dev?namespace=rester-plain-dev&kind=GitRepository", "status": 500}
2023-09-19T11:37:10.162Z	ERROR	gitops	middleware/middleware.go:39	server error	{"error": "cluster= not found"}
2023-09-19T11:37:10.162Z	INFO	gitops	middleware/middleware.go:65	server error	{"uri": "/v1/object/rester-kustomize-dev?namespace=rester-kustomize-dev&kind=GitRepository", "status": 500}
2023-09-19T11:37:10.164Z	ERROR	gitops	middleware/middleware.go:39	server error	{"error": "cluster= not found"}
2023-09-19T11:37:10.164Z	INFO	gitops	middleware/middleware.go:65	server error	{"uri": "/v1/object/rester-kustomize-test?namespace=rester-kustomize-test&kind=GitRepository", "status": 500}
2023-09-19T11:37:10.164Z	ERROR	gitops	middleware/middleware.go:39	server error	{"error": "cluster= not found"}
2023-09-19T11:37:10.164Z	INFO	gitops	middleware/middleware.go:65	server error	{"uri": "/v1/object/rester-helm-test?namespace=rester-helm-test&kind=GitRepository", "status": 500}

[opudrovs]

@Cajga thank you for confirming the issue and providing additional info!

[opudrovs]

It is possible it is not a frontend issue, I just came across it while testing another frontend issue.