solo-io / gloo-portal-issues

Public tracker for issues related to Gloo Portal
https://docs.solo.io/gloo-portal/latest/
1 stars 3 forks source link

Portal Dashboard shows blank Overview tab #76

Open jameshbarton opened 3 years ago

jameshbarton commented 3 years ago

Describe the bug The Overview tab on the Portal Dashboard shows a blank panel.

I'm experimenting with adding a new header (foo: bar) in a requestTransformation and cannot get it to apply to the request. I began with an example like the standard Portal docs but modified it to use httpbin as upstream rather than petstore. The basics work fine. I can access it use api-key authNZ from both CLI and portal UI. I then tried to use the new request transformation integration at the route level with Edge. The user transformation does not appear to be merged into the generated RouteTable alongside the Portal-generated transforms.

However, the Portal-generated RouteTable appears to have invalid transformation syntax in it, per the error in the portal UI controller logs.

To Reproduce Note that this config is deployed in a solo-test GKE project. You can also reproduce it from artifacts in the attached zip.

  1. Port-forward the admin-server UI to localhost. kubectl port-forward -n gloo-portal svc/gloo-portal-admin-server 8080:8080

  2. Point browser to localhost:8080/overview

  3. Observe the blank panel. Note this error message in the gloo-portal-admin-server logs, which seems to derive from an incorrectly generated RouteTable:

    E0708 16:53:54.359105       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.20.4/tools/cache/reflector.go:167: Failed to  watch *v1beta1.APIProduct: failed to list *v1beta1.APIProduct: v1beta1.APIProductList.Items: []v1beta1.APIProduct: v1beta
    1.APIProduct.Status: Spec: unmarshalerDecoder: unknown field "early" in gloo.solo.io.RouteOptions, error found in #10 byte of ...|le":{}}}]},"status":|..., bigger context ...|bar"}}}}]}}}}},"name":"v1","tags":{"stable":{}}}]},"status":{"modifiedDate":"2021-07-06T21:26:48.459|...

    See the generated RouteTable in the attached zip that contains the APIDoc, APIProduct that specifies the route-level transform, Environment, the generated RT and VS, and the Envoy proxy config.

  4. Note that there are several other UI anomalies in the portal dashboard under this scenario. These likely stem from the same root cause, so I'm not creating separate tickets for each. But they all should be checked.

Expected behavior The Overview panel (and other UI elements) displays correctly.

Additional context