b764f52ab9
In a deployment with two groups (ex. A and B), if group A's canary becomes healthy before group B's, the deadline for the overall deployment will be set to that of group A. When the deployment is promoted, if group A is done it will not contribute to the next deadline cutoff. Group B's old deadline will be used instead, which will be in the past and immediately trigger a deployment progress failure. Reset the progress deadline when the job is promotion to avoid this bug, and to better conform with implicit user expectations around how the progress deadline should interact with promotions. |
||
|---|---|---|
| .. | ||
| autopilot.go | ||
| autopilot_test.go | ||
| deployment_events_test.go | ||
| events.go | ||
| events_test.go | ||
| iterator.go | ||
| schema.go | ||
| schema_test.go | ||
| state_changes.go | ||
| state_store.go | ||
| state_store_oss.go | ||
| state_store_test.go | ||
| testing.go | ||