-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
OpenShift 4.16
-
None
-
None
-
False
-
-
False
-
NEW
-
NEW
-
Before this fix, if a custom datasource defined on a dashboard was not found the data was fetched from the default datasource. After the fix, an error is displayed instead.
-
Bug Fix
-
-
-
Sprint 252, Sprint 253
when using the monitoring plugin with the console dashboards plugin, if a custom datasource defined in a dashboard is not found, the default in cluster prometheus is used to fetch data. This creates a false assumption to the user that the custom dashboard is working when in reality, it should fail.
How to reproduce:
- In OpenShift 4.16
- Install COO
- Enable the console dashboards plugin as documented here
- Create a dashboard that uses custom datasources as documented here. Do not create a datasource so the bug can be reproduced
- Go to monitoring -> dashboards and select the dashboard created above
Expected result
The dashboard should display an error as the custom datasource was not found
- is cloned by
-
OU-417 [release-4.15] When custom datasource is not found it should not fallback to the default in cluster prometheus
- Verified
- links to