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

service account token deleted, Plugin settings updated on every refresh #3566

Closed
ToonTijtgat2 opened this issue Dec 14, 2023 · 4 comments
Closed
Assignees
Labels
bug Something isn't working more info needed

Comments

@ToonTijtgat2
Copy link

What went wrong?

What happened:

  • Every time I try to refresh the alert-groups page I receive a popup stating service account token deleted, Plugin settings updated
    Capture

This also happens when I sent the alert group url to someone: for example https://url/a/grafana-oncall-app/alert-groups/I1AWEDEVZHU44?perpage=25&start=1

When opening the url in the browser, you shorly see the alertgroup and then the popup appears and you are rerouted to the alert-groups page.

What did you expect to happen:

  • I would be nice to be able to sent links from alert-groups to college's.

How do we reproduce it?

  1. Open Grafana OnCall and refresh your page.
  2. copy the url of an alertgroup and open it again in a new window.

Grafana OnCall Version

1.3.78

Product Area

Other

Grafana OnCall Platform?

Kubernetes

User's Browser?

No response

Anything else to add?

No response

@ToonTijtgat2 ToonTijtgat2 added the bug Something isn't working label Dec 14, 2023
@ToonTijtgat2
Copy link
Author

noticed that oncall plugin creates a new service account in grafana every time we refresh the page.
Capture

@via-justa
Copy link

I'm seeing the same thing on grafana 10.2.2 and oncall 1.3.77 (both deployment and plugin)
We also have an issue where non-admin users cannot use oncall (see screenshot) that I suspect relates to that.
@ToonTijtgat2 are you seeing the same issue with non-admin users?
image

@clementduveau
Copy link

Those 2 issues (#3607 and #3566) are related. Service accounts from admin users will succeed, and therefore admins are not affected by the bug.

@mderynck
Copy link
Contributor

mderynck commented Feb 9, 2024

This was resolved by keeping mirageSecretKey constant through an external secret.

@mderynck mderynck closed this as completed Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working more info needed
Projects
None yet
Development

No branches or pull requests

5 participants