Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of allow unhealthy canaries without blocking autopromote into release/1.3.x #14015

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #14001 to be assessed for backporting due to the inclusion of the label backport/1.3.x.

The below text is copied from the body of the original PR.


fixes #8150

One thing I'm not 100% about this is if the test is correct. If I'm reading everything from copy/pasting the other one and understanding the data model this should "just work," because we're never setting c3 to healthy, so that should test this exact bit of logic (where we want 2 healthy canaries, have 3 placed, and only 2 are ever promoted to healthy).

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/allow_failed_canaries_autopromote/barely-desired-hamster branch from 5264638 to 71c64e0 Compare August 4, 2022 15:58
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 2c5a8d0 into release/1.3.x Aug 4, 2022
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/allow_failed_canaries_autopromote/barely-desired-hamster branch August 4, 2022 15:58
@github-actions
Copy link

github-actions bot commented Dec 3, 2022

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

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants