Backport of ui: fix Topology node state filter into release/1.5.x #17999
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-nomad-core
force-pushed
the
backport/b-ui-fix-topo-node-state/frequently-vast-locust
branch
from
9072fed
to
9a30e37
Compare
|
|
"Ineligible" and "Draining" are not determined by the node status, but are rather inferred from other fields.
lgfa29
force-pushed
the
backport/b-ui-fix-topo-node-state/frequently-vast-locust
branch
from
f77b766
to
04414ec
Compare
Ember Test Audit comparison
|
lgfa29
approved these changes
Jul 19, 2023
lgfa29
deleted the
backport/b-ui-fix-topo-node-state/frequently-vast-locust
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #17940 to be assessed for backporting due to the inclusion of the label backport/1.5.x.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
"Ineligible" and "Draining" are not determined by the node status, but are rather inferred from other fields.
Closes #17772