You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After successful canary analysis Flagger reports successful canary promotion, but it doesn't copy the canary spec to the primary. That means that Flagger reports success, but the deployed app, after the promotion, is at the old version.
Steps to reproduce:
Define maxWeight and stepWeight in such a way that the former is not a multiple of the latter.
This might be a misuse or something I've missed in documentation, but in end of the day the behaviour seems dangerous - report success and fail to do the job. I assume it should be safe to change the == condition to >=. If it is not then maybe a ValidatingWebhook can be implemented for this case?
istio 1.1.6, k8s - 1.11.9, flagger - 0.13.2
After successful canary analysis Flagger reports successful canary promotion, but it doesn't copy the canary spec to the primary. That means that Flagger reports success, but the deployed app, after the promotion, is at the old version.
Steps to reproduce:
I believe this is the block of code which is causing the problem: https://github.com/weaveworks/flagger/blob/12d84b2e241438e4088f65eeecbcb850fba3f222/pkg/controller/scheduler.go#L362-L370
This might be a misuse or something I've missed in documentation, but in end of the day the behaviour seems dangerous - report success and fail to do the job. I assume it should be safe to change the
==
condition to>=
. If it is not then maybe a ValidatingWebhook can be implemented for this case?Flagger logs in failure scenario (
maxWeight
= 61,stepWeight
= 15):Flagger logs in success scenario (
maxWeight
= 45,stepWeight
= 15):The text was updated successfully, but these errors were encountered: