Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timezone information is not included in mimir and mimirtool #4582

Closed
nasonfish opened this issue Mar 23, 2023 · 0 comments · Fixed by #4583
Closed

Timezone information is not included in mimir and mimirtool #4582

nasonfish opened this issue Mar 23, 2023 · 0 comments · Fixed by #4583

Comments

@nasonfish
Copy link
Contributor

Describe the bug

When using Location for muting rules in alertmanager using the docker images grafana/mimirtool and grafana/mimir, they are not aware of any timezones.

To Reproduce

Steps to reproduce the behavior:

  1. Create an alertmanager configuration with a silencing rule using location: America/Denver
  2. Run mimirtool alertmanager verify on your alertmanager configuration
mimirtool: error: unknown time zone America/Denver, try --help

If you get past this and apply to a running Mimir instance, you get this error:

mimirtool: error: POST request to https://mimir.<redacted>/api/v1/alerts failed: server returned HTTP status: 400 Bad Request, body: "error validating Alertmanager config: unknown time zone America/Denver\n", try --help

Expected behavior

This timezone should be recognized by default and an alerting rule should be able to be created.

Environment

  • Infrastructure: Kubernetes
  • Deployment tool: GitLab CI

Additional Context

Populating the /usr/share/zoneinfo directory seems to fix the problem, which can be done easily in alpine using apk add tzdata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant