Document cases when auto_promtoe = false canary deploy, will auto promote

[drewbailey]

Issue

There are a few cases when a canary deploy, with auto_promote = false will in fact automatically deploy.

The two primary cases are initial deploys, and a healthy canary deploy which occurs after a previously failed deploy.

[stale]

Hey there

Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this.

Thanks!

[stale]

Hey there

Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this.

Thanks!

[davemay99]

Documented in #8439 --
When a canary deployment is in progress, and a preexisting / stable version allocation is stopped, I expect Nomad to create a replacement allocation using the stable version of the jobspec. Instead, Nomad incorrectly deploys the unpromoted canary version.