Zone_rules_exception "Unknown time-zone ID: Browser" on Kibana

Hi team,

did anyone of you experienced this issue on Kibana whenever you upgrade to the latest version of ODFE. Currently, I’m using ODFE v 1.13.2. This doesn’t happen when using Browser as a default time zone but rather when changing it to e.g. “UTC” and upgrading the ODFE version. It may be related to the cache and it gets resolved by doing “force refresh” e.g. on Chome via Ctrl + R. I just wanted to report it in case the ODFE team wants to debug a bit further on the issue.

Here is the error user gets on Kibana:

Unknown time-zone ID: Browser
Error: Bad Request
    at Fetch._callee3$ (https://<host>/36136/bundles/core/core.entry.js:6:59535)
    at tryCatch (https://<host>/36136/bundles/plugin/opendistroQueryWorkbenchKibana/opendistroQueryWorkbenchKibana.plugin.js:1:32004)
    at Generator.invoke [as _invoke] (https://<host>/36136/bundles/plugin/opendistroQueryWorkbenchKibana/opendistroQueryWorkbenchKibana.plugin.js:1:35968)
    at Generator.forEach.prototype.<computed> [as next] (https://<host>/36136/bundles/plugin/opendistroQueryWorkbenchKibana/opendistroQueryWorkbenchKibana.plugin.js:1:33129)
    at fetch_asyncGeneratorStep (https://<host>/36136/bundles/core/core.entry.js:6:52652)
    at _next (https://<host>/36136/bundles/core/core.entry.js:6:52968)

and it seems to be coming mostly from opendistroQueryWorkbenchKibana GitHub - opendistro-for-elasticsearch/sql: 🔍 Open Distro for Elasticsearch SQL Plugin .

Best regards,

[Moved this to SQL category.]

That’s a really interesting, actually. I suspect the Kibana/Dashboard plugin is somehow parsing something incorrectly in this edge case.

Would you mind filing a bug on the SQL repo? (You might get bounced to OpenSearch SQL: GitHub - opensearch-project/sql)

1 Like

Hey @searchymcsearchface ,

sure, will create an issue over there.