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

CLI command to display the agents fingerprint(s) #117

Closed
catsby opened this issue Sep 25, 2015 · 5 comments
Closed

CLI command to display the agents fingerprint(s) #117

catsby opened this issue Sep 25, 2015 · 5 comments

Comments

@catsby
Copy link
Contributor

catsby commented Sep 25, 2015

For operating or debugging, it would be helpful if I could run a command on a node and get some information on the results of the Fingerprints, both which ones ran, and what they recorded. This would be helpful for understanding why a job isn't placing where I thought it would, or debugging a Fingerprint.

Ex:

$ nomad node-status -fingerprint
Fingerprints ran:
- Java
  - version: 1.7...
- Docker
- CPU:
  - cores: 24
  - mhz: 9001
- Blah..
- Blah
@catsby catsby added this to the Future milestone Sep 25, 2015
@ryanuber
Copy link
Member

Definitely want! 👍 Should be a pretty simple addition.

@cbednarski
Copy link
Contributor

Also since the fingerprints all set node attributes, maybe there's a way we can just dump all of the node attributes and their current values?

@iverberk
Copy link
Contributor

Is there still a need for the -fingerprint flag or is this fixed by #313? Otherwise I'd like to take a stab at implementing the flag.

@dadgar
Copy link
Contributor

dadgar commented Oct 26, 2015

I think it is largely solved by that PR. I think it is best we close this PR. Thanks so much!

@dadgar dadgar closed this as completed Oct 26, 2015
benbuzbee pushed a commit to benbuzbee/nomad that referenced this issue Jul 21, 2022
This is the main patch for hashicorp#117. It still has several outstanding problems that
we'll work through in later commits, but it's good enough to discuss.
benbuzbee pushed a commit to benbuzbee/nomad that referenced this issue Jul 21, 2022
Reworks membership changes for one in process at any time.
@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 Dec 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants