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

Events are not created when alert manager is unable to create the alert due to error #26

Open
phanipadala opened this issue Sep 15, 2021 · 1 comment

Comments

@phanipadala
Copy link
Contributor

phanipadala commented Sep 15, 2021

Is this a BUG REPORT or FEATURE REQUEST?:
Bug

What happened:
When there is an invalid value passed as param [Eg: severity value as "warning" instead of "warn"] , controller will not create wavefront alert and show error in controller logs . Currently we dont see events generated for the error.

What you expected to happen:
We should see error message in the events when we use kubectl kubectl get events .

How to reproduce it (as minimally and precisely as possible):
In Alerts config , pass invalid severity value as "warning" and try to apply it.

Anything else we need to know?:

Environment:

  • alert-manager version
  • Kubernetes version :
$ kubectl version -o yaml

Other debugging information (if applicable):

- controller logs:

$ kubectl logs

@mnkg561
Copy link
Collaborator

mnkg561 commented Sep 29, 2021

i was checking the logs and looks like we need patch access as well for events.

'events "fluentd-errors.16a8297caa6d370d" is forbidden: User "system:serviceaccount:alert-manager-system:alert-manager-controller-manager" cannot patch resource "events" in API group "" in the namespace "dev-iksmanager-usw2-ldev"' (will not retry!)

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

No branches or pull requests

2 participants