Notifications - Events not triggering message to Slack

[egkelly]

Checklist:

• [x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [x] I've included steps to reproduce the bug.
• [x] I've pasted the output of argocd version.

Describe the bug

I've set up Slack notifications according to the documentation (with a few tweaks given the helm chart version I have deployed - 2.16.0 ), but the events I have triggers/templates set up for are not actually triggering messages to slack. I've run through all the troubleshooting and verified that argocd admin notifications template notify app-deployed appName --recipient slack:mychannel sends messages as expected. I have also annotated all of my applications with notifications.argoproj.io/subscribe.on-deployed.slack: mychannel.

To Reproduce

• Install argocd via helm, chart version 2.16.0. I had to update the notifications role and notifications configmap due to a few bugs in the helm chart version.

  argocd-notifications-cm

  kind: ConfigMap
  metadata:
  name: argocd-notifications-cm
  namespace: ${local.namespace}
  data:
  service.slack: |
    token: ${var.slack_token}
  template.app-deployed: |
    message: |
      {{if eq .serviceType "slack"}}:white_check_mark:{{end}} Application {{.app.metadata.name}} is now running new version of deployments manifests.
    slack:
      attachments: |
        [{
          "title": "{{ .app.metadata.name}}",
          "title_link":"{{.context.argocdUrl}}/applications/{{.app.metadata.name}}",
          "color": "#18be52",
          "fields": [
          {
            "title": "Sync Status",
            "value": "{{.app.status.sync.status}}",
            "short": true
          },
          {
            "title": "Repository",
            "value": "{{.app.spec.source.repoURL}}",
            "short": true
          },
          {
            "title": "Revision",
            "value": "{{.app.status.sync.revision}}",
            "short": true
          }
          {{range $index, $c := .app.status.conditions}}
          {{if not $index}},{{end}}
          {{if $index}},{{end}}
          {
            "title": "{{$c.type}}",
            "value": "{{$c.message}}",
            "short": true
          }
          {{end}}
          ]
        }]
  trigger.on-deployed: |
    - description: Application is synced and healthy. Triggered once per commit.
      oncePer: app.status.operationState.syncResult.revision
      send:
      - app-deployed
      when: app.status.operationState.phase in ['Succeeded'] and app.status.health.status
        == 'Healthy'

  argocd notifications controller role

  kind: Role
  metadata:
  annotations:
    meta.helm.sh/release-name: argo-cd
    meta.helm.sh/release-namespace: argocd
  labels:
    app.kubernetes.io/component: notifications-controller
    app.kubernetes.io/instance: argo-cd
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: argocd-notifications-controller
    app.kubernetes.io/part-of: argocd
    helm.sh/chart: argo-cd-5.2.0
  name: argo-cd-argocd-notifications-controller
  namespace: argocd
  rules:
  - apiGroups:
  - argoproj.io
  resources:
  - applications
  - appprojects
  verbs:
  - get
  - list
  - watch
  - update
  - patch
  - apiGroups:
  - ""
  resources:
  - configmaps
  - secrets
  verbs:
  - list
  - watch
  - get
  - apiGroups:
  - ""
  resourceNames:
  - argocd-notifications-controller-cm
  - argocd-notifications-cm
  resources:
  - configmaps
  verbs:
  - get
  - apiGroups:
  - ""
  resourceNames:
  - argocd-notifications-controller-secret
  - ${local.notifications_secret}
  resources:
  - secrets
  verbs:
  - get

• Annotate application with notifications.argoproj.io/subscribe.on-deployed.slack: mychannel

• Test notifications by exec-ing into the notifications pod argocd admin notifications template notify app-deployed appName --recipient slack:mychannel

  Slack channel receives the message

• Push a new version of the application image and deploy via ArgoCD Slack channel does not receive the message

  Notifications pod logs show the following:

  time="2022-10-14T15:59:32Z" level=info msg="Trigger on-deployed result: []" resource=argocd/my-application
  time="2022-10-14T15:59:32Z" level=info msg="Processing completed" resource=argocd/my-application

  So far I haven't found any documentation on what the above means, though I imagine the empty brackets aren't a good sign?

Expected behavior

Message is sent to slack on deployment.

Version

ArgoCD version 5.2.0

Helm Chart Version 2.16.0

[4wdonny]

Out of curiosity, if you remove and app.status.health.status == 'Healthy' from the when block, does it work? I've been having issues with the and app.status.health.status == 'Healthy' portion and wondering if it is the same issue.

[arturzielinskicard]

Please check arguments passed to commandline of argocd-notifications-controller: secret-name config-map-name Is it match your config and secret name? For debug you can start notification service with loglevel debug

[shreyasgune]

G'day @egkelly , I was looking an issue very similar to this and I ended up getting it to work by modifying my template.

I am curious about one thing.

The

data:
  service.slack: |
    token: ${var.slack_token}

reference. I know that the secret is defined in

apiVersion: v1
kind: Secret
metadata:
  name: argocd-notifications-secret
stringData:
  slack-token: <base64 encoded auth-token>

but I'm wondering how the configmap knows about the value of $slack-token. How does that "fetching of the value of slack-token" happen behind the scenes?

[shreyasgune]

G'day @egkelly , I was looking an issue very similar to this and I ended up getting it to work by modifying my template.

I am curious about one thing.

The

data:
  service.slack: |
    token: ${var.slack_token}

reference. I know that the secret is defined in

apiVersion: v1
kind: Secret
metadata:
  name: argocd-notifications-secret
stringData:
  slack-token: <base64 encoded auth-token>

but I'm wondering how the configmap knows about the value of $slack-token. How does that "fetching of the value of slack-token" happen behind the scenes?

okay, so there may have been a thing in an older version of the helm-chart that did that secret bit. I think so.