[Placeholder] Allocations may fail to be upgraded

[notnoop]

This is a placeholder issue for investigating a case where an allocation did not get stopped when a job update is submitted. In one case, after a job update and the deployment is promoted, new allocations were placed as expected, but a single old allocation is left running and not stopped. The operator needed to explicitly shut the allocation down.

Will update this ticket with more details and fixes as we find them.

[notnoop]

We addressed the symptyms in #8886 . We haven't been able to reproduce the case or have a bug report against a modern version of Nomad, so closing this issue.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.