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

OSS Grafana OnCall doesnt pick settings from ENV #5222

Open
Mdumala opened this issue Oct 31, 2024 · 3 comments
Open

OSS Grafana OnCall doesnt pick settings from ENV #5222

Mdumala opened this issue Oct 31, 2024 · 3 comments

Comments

@Mdumala
Copy link

Mdumala commented Oct 31, 2024

What went wrong?

What happened:

  • After configure entire flow on grafana OSS i run a prepared alert with notification via email
  • But in grafana oncall celery i can see :
    oncall 2024-10-31 12:57:01,043 source=engine:celery worker=ForkPoolWorker-2 task_id=03b10dad-0318-47a2-b4d2-6fd109fd3765 task_name=apps.email.tasks.notify_user_async name=apps.email.tasks level=ERROR Error ││ while sending email: empty EMAIL_HOST env variable
  • If i put these configuration direct to Value it works perfectly -> which clearly tell us that parameter from Value work but not from ENV
  • It looks like it doesnt pick values from ENV column

What did you expect to happen:

  • That values passed through ENV will be take by Grafana On Call

Image

How do we reproduce it?

  1. Configure smtp properties inside helm chart to Grafana OnCall
  2. Verify that these parameters are visible on OnCall->Settings->Env Variables
  3. Try to send demo alerts to configured user with rights email
  4. Email reach its recipient

Grafana OnCall Version

v1.11.3

Product Area

Alert Flow & Configuration

Grafana OnCall Platform?

Kubernetes

User's Browser?

No response

Anything else to add?

No response

@bpedersen2
Copy link

Did you restart the celery pods? Only changing config values in the may not restart everything, but for the pods to pick up new secrets/ configmaps they need a restart.

@maffelbaffel
Copy link

Having the same problem. Restarting celery pods has no effect. Values are clearly picked up as env variables but still shown as status "empty".

@amine-mokaddem
Copy link

Same thing here with version : v1.13.9

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

No branches or pull requests

4 participants