-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
-
False
-
Unset
-
No
-
-
Specifically we expect this API to automatically fork the base template for us:
GET /api/chrome-service/v1/dashboard-templates?dashboard=landingPage
However the API returns the following error:
"ERROR: null value in column \"sx\" of relation \"dashboard_templates\" violates not-null constraint (SQLSTATE 23502)"
We recently delivered a change that fixes a typo in the DB - `sx` was renamed to `sm`: https://github.com/RedHatInsights/chrome-service-backend/pull/398
I suspect we may need to delete that relation/table and recreate it on stage to resolve the issue. The API works as expected for me locally after deleting/recreating my podman machine.
Reproduction: the UI for widgetized frontend is not yet delivered. This is reproducible with the insights-qa user. This issue can be reproduced via postman or CuRL by sending:
GETÂ
https://console.stage.redhat.com/api/chrome-service/v1/dashboard-templates?dashboard=landingPage
You must have squid proxy configured in postman. The `Authorization` header must be sent with the request.
- impacts account
-
RHCLOUD-29577 Landing page gets widgetized
- Closed