Open dinhdobathi1992 opened 1 year ago
@dinhdobathi1992 is the engine pod reachable from Grafana pod after you change the config?
Recently we made some changes to the way Grafana OnCall is initialized. Use 1.9.22, there were quite a few changes along the way from 1.9.0-1.9.22 to get things working.
externalServiceAccounts
feature toggle enabled.
This has already been enabled in the docker compose files and helm charts in the oncall repo.curl -X POST 'http://admin:admin@localhost:3000/api/plugins/grafana-oncall-app/settings' -H "Content-Type: application/json" -d '{"enabled":true, "jsonData":{"stackId":5, "orgId":100, "onCallApiUrl":"http://engine:8080/", "grafanaUrl":"http://grafana:3000/"}}'
curl -X POST 'http://admin:admin@localhost:3000/api/plugins/grafana-oncall-app/resources/plugin/install'
Grafana OnCall should now be ready to use. For additional troubleshooting see here
I'm installing on-call by helm, everything is normal after the first deploy and configure plugin. The problem is :
When we modified the configuration of helm such as
replicas
,resource request
, and try to redeploy by helm, italways
required me toreconfigure plugin
. It said:invalid Invitation Token
and ask me to re-generate anotherInvitation Token
.If I repeat the whole steps, it should be fine, but this maybe not an expected behavior since we already get the Invitation Token and using the same database.
About the version:
Oncall :
v1.1.0
Oncall-plugin:1.1.0
External DB:postgres
instance.