I am seeing below error during rollouts of all the applications I have but able to receive notification on slack. I also checked the configuration, all the triggers and templates are setup correctly. One thing to know here in my setup argo rollout exists in argo-rollouts namespace whereas the applications exists in a different namespace.
Notifications failed to send for eventReason RolloutStepCompleted with error: trigger 'on-rollout-step-completed' is not configured
To Reproduce
I've deployed argo-rollout via the official helm chart, this is the values.yaml file -
There should not be any error in the logs as we already have the required configuration and also the notification is working fine.
Screenshots
Version
1.6.0
Logs
# Paste the logs from the rollout controller
# Logs for the entire controller:
kubectl logs -n argo-rollouts deployment/argo-rollouts
# Logs for a specific rollout:
kubectl logs -n argo-rollouts deployment/argo-rollouts | grep rollout=<ROLLOUTNAME
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
Any updates on this issue , we still facing the same issue .
Notifications failed to send for eventReason RolloutPaused with error: [trigger 'on-rollout-paused' is not configured]
Checklist:
Describe the bug
I am seeing below error during rollouts of all the applications I have but able to receive notification on slack. I also checked the configuration, all the triggers and templates are setup correctly. One thing to know here in my setup argo rollout exists in argo-rollouts namespace whereas the applications exists in a different namespace.
To Reproduce
With the above values file I am able to see notification configmap and secrets generated perfectly fine -
Expected behavior
There should not be any error in the logs as we already have the required configuration and also the notification is working fine.
Screenshots
Version
1.6.0
Logs
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.