[BUG] Invalid memory address on Kubernetes v1.24 #336
Comments
|
Hi, I found out that this error is produced when the executables working directory does not contain the card template. Check the working directory contains the provided template file and is readable by the user running the service |
|
Circling back on this... customCardTempalate: |
{{ define "teams.card" }}
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"themeColor": "{{- if eq .Status "resolved" -}}2DC72D
{{- else if eq .Status "firing" -}}
{{- if eq .CommonLabels.severity "critical" -}}8C1A1A
{{- else if eq .CommonLabels.severity "warning" -}}FFA500
{{- else -}}808080{{- end -}}
{{- else -}}808080{{- end -}}",
"summary": "{{ .CommonAnnotations.summary }}",
"title": "Prometheus Alert ({{ .Status }})",
"sections": [ {{$externalUrl := .ExternalURL}}
{{- range $index, $alert := .Alerts }}{{- if $index }},{{- end }}
{
"activityTitle": "[{{ $alert.Annotations.description }}]({{ $externalUrl }})",
"facts": [
{{- range $key, $value := $alert.Annotations }}
{
"name": "{{ reReplaceAll "_" "\\\\_" $key }}",
"value": "{{ reReplaceAll "_" "\\\\_" $value }}"
},
{{- end -}}
{{$c := counter}}{{ range $key, $value := $alert.Labels }}{{if call $c}},{{ end }}
{
"name": "{{ reReplaceAll "_" "\\\\_" $key }}",
"value": "{{ reReplaceAll "_" "\\\\_" $value }}"
}
{{- end }}
],
"markdown": true
}
{{- end }}
]
}
{{ end }}But the error remains. Am I missing something from the docs maybe? |
|
Ok it's solved. Solved by using Helm CLI and the default installation command. For context, this was happening with Rancher v2.7.1 as well with v2.7.6 |
Describe the bug
Deployed a fresh new install with Helm, chart v1.3.4 attempting to migrate from a v1.20 Kubernetes cluster.
The deployment is successful and pods are running but log is filled with these messages:
Also, when calling a receiver with cURL I do have an empty response message:
Version
Helm Chart v1.3.4, image is
quay.io/prometheusmsteams/prometheus-msteams:v1.5.2To Reproduce
Install the chart via Rancher 2.7.1 on an RKE1 cluster, Kubernetes version 1.24
Expected behavior
Running without nil pointer reference errors.
Additional context
Same deployment with same values file works fine on RKE1 Kubernetes v1.20 on Rancher 2.5
The text was updated successfully, but these errors were encountered: