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

nomad operator debug: incorrect node count summary #9566

Closed
davemay99 opened this issue Dec 8, 2020 · 1 comment · Fixed by #9625
Closed

nomad operator debug: incorrect node count summary #9566

davemay99 opened this issue Dec 8, 2020 · 1 comment · Fixed by #9625
Assignees
Labels

Comments

@davemay99
Copy link
Contributor

When nomad operator debug filters client nodes, I expect the summary to reflect (<filtered-count>/<total-count>). Instead the total count is inconsistent.

For example, the total number of clients in this cluster is actually 3, but the summary shows (2/1) which translates into "2 clients selected out of 1 total"

nomad operator debug -duration 5s -server-id leader -node-id b5,20
Starting debugger...

          Servers: (1/3) [leader]
          Clients: (2/1) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
...
@davemay99 davemay99 self-assigned this Dec 8, 2020
@tgross tgross added the type/bug label Dec 8, 2020
davemay99 added a commit that referenced this issue Dec 11, 2020
@davemay99 davemay99 linked a pull request Dec 12, 2020 that will close this issue
davemay99 added a commit that referenced this issue Dec 14, 2020
* debug: update test to identify bug in GH-9566
* debug: range tests need fresh cmd each iteration
* debug: fix node count bug in GH-9566
schmichael pushed a commit that referenced this issue Dec 16, 2020
* debug: update test to identify bug in GH-9566
* debug: range tests need fresh cmd each iteration
* debug: fix node count bug in GH-9566
@github-actions
Copy link

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.

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

Successfully merging a pull request may close this issue.

2 participants