notification trigger.on-rollout-aborted is sending twice, is that normal? #1964
Replies: 2 comments 2 replies
-
Hi @juanvasquezreyes, have you found the cause of this issue? Or maybe an alternative solution? We are affected by this issue in one of our environments and we also tried the oncePer condition without success. The weirdest part is the same configuration in other environments behaves as expected even without having to use the oncePer condition. |
Beta Was this translation helpful? Give feedback.
-
We're seeing this with rollouts 1.5.1, it's consistent for all apps. We only have 1 argo-rollouts replica, and 1 argo-rollouts-dashboard replica. We have this in the notifications ConfigMap, I'm wondering if the abort is done automatically and we're causing the 2nd one my specifying it in here?
|
Beta Was this translation helpful? Give feedback.
-
I'm using the trigger on-rollout-aborted for notification, but the notification when a rollout is aborted is being sent twice, is that normal? with milliseconds difference
I tried adding oncePer option by version but still is sending notification twice
I added the phase for tracking purposes and in one notification the rollout phase is "Progressing" the other one is "degraded"
Beta Was this translation helpful? Give feedback.
All reactions