search

grafana / oncall

Developer-friendly incident response with brilliant Slack integration
GNU Affero General Public License v3.0
3.44k stars 276 forks source link

Issue when trying to install with helm #98

Closed PatMis81 closed 2 years ago

PatMis81 commented 2 years ago

Hi, I have encountered an issue when trying to install the helm chart on my local kubernetes. I get the following message:

Error: INSTALLATION FAILED: template: oncall/templates/engine/job-migrate.yaml:48:14: executing "oncall/templates/engine/job-migrate.yaml" at <include "snippet.redis.env" .>: error calling include: templa te: oncall/templates/_env.tpl:157:12: executing "snippet.redis.env" at <include "snippet.redis.host" .>: error calling include: template: oncall/templates/_env.tpl:140:46: executing "snippet.redis.host" a t <.Values.externalRedis.host>: nil pointer evaluating interface {}.host

Regards, Patrick

andy812 commented 2 years ago

Solution: change external_redis to externalRedis in values.yaml

PatMis81 commented 2 years ago

Thank you Andy! This worked!

andy812 commented 2 years ago

Be careful, there's a lot of errors: nginx-ingress instead of ingress-nginx, cert issuer issue, etc. Please, don't close this bug until it will be fixed by Grafana team.

PatMis81 commented 2 years ago

Reopen for several bugs to be fixed by Grafana.

idv-Evgenii commented 2 years ago

Hi, this error appears at startup and at the same time it starts everything except oncall celery and oncall engine, it initializes under oncall, but does not start

Error: INSTALLATION FAILED: failed post-install: warning: Hook post-install oncall/templates/cert-issuer.yaml failed: Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post "https://******.svc:443/mutate?timeout=30s": service "test-cert-manager-webhook" not found

but nevertheless it starts grafana and I also wanted to clarify where you can get an invite token for the oncall plugin for use helm?

francis-cassbana commented 2 years ago

Hi , I have disabled ingress false, eventhough its trying to install ingress in default namespace , i have ingress running in default namespace and trying to install oncall in monitoring namespace and disabled ingress getging below error Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: IngressClass "nginx" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "oncall": current value is "ingress"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "monitoring": current value is "default"

idv-Evgenii commented 2 years ago

@francis-cassbana Hello, try changing the name from nginx-ingress to ingress-nginx in values.yaml (that is, the name of the archive that is in the chart folder)

francis-cassbana commented 2 years ago

Hi @idv-Evgenii i changed to ingress-nginx still same error !! i have ingress controller and cert manager already installed in the cluster so i disabled it to false eventhough its trying to install it Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: IngressClass "nginx" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "oncall": current value is "ingress"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "monitoring": current value is "default"

billmetangmo commented 2 years ago

The issue seems to be related to the version of k8s installed by default right now by minkube which is v1.25+ . I installed v1.21.4 instead minikube start --kubernetes-version=v1.21.14 and it's working.

Matvey-Kuk commented 2 years ago

We added this task to the core team's backlog.

iskhakov commented 2 years ago