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.

Sign up for GitHub

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

Jump to bottom

Show node names instead of node ids in nomad status #1180

Closed
tantra35 opened this issue May 17, 2016 · 5 comments
Closed

Show node names instead of node ids in nomad status #1180

tantra35 opened this issue May 17, 2016 · 5 comments
Labels
stage/thinking theme/cli type/enhancement

Comments

@tantra35
Copy link
Contributor

It will be cool if in nomad status command show node names, now it show node is and it's not very convenient
@camerondavison
Copy link
Contributor

I wonder if something like --format api (https://docs.docker.com/engine/reference/commandline/ps/#formatting) that docker has would be a good way to accomplish this. So that it would be possible to change how some of the CLI command output information

@ketzacoatl
Copy link
Contributor

This generally doesn't matter when things are working ok, but when stuff breaks.. I find myself frequently needing to grab IDs to translate to a node name to do some remote exec in consul - I would love a flag or option to specify node name in the status displays (I'd support that as a default, but maybe others don't like that).

@salkin
Copy link

salkin commented Mar 3, 2017

This would be great to have, now I often find myself executing two commands to find the real host for a task that is failing or misbehaving.

jrasell added a commit to jrasell/nomad that referenced this issue Jul 17, 2018
@jrasell
Add NodeName to the alloc/job status outputs.
e1e019a 
Currently when operators need to log onto a machine where an alloc
is running they will need to perform both an alloc/job status
call and then a call to discover the node name from the node list.

This updates both the job status and alloc status output to include
the node name within the information to make operator use easier.

Closes hashicorp#2359
Cloess hashicorp#1180
@jrasell jrasell mentioned this issue Jul 17, 2018
Closed
@arshjohar arshjohar mentioned this issue Jan 22, 2019
Merged
@arshjohar
Copy link
Contributor

We merged a PR that should display Node Name for job status and alloc status commands. Closing this one.

preetapan pushed a commit that referenced this issue Mar 4, 2019
@jrasell @preetapan
Add NodeName to the alloc/job status outputs.
653595a 
Currently when operators need to log onto a machine where an alloc
is running they will need to perform both an alloc/job status
call and then a call to discover the node name from the node list.

This updates both the job status and alloc status output to include
the node name within the information to make operator use easier.

Closes #2359
Cloess #1180
preetapan pushed a commit that referenced this issue Mar 25, 2019
@jrasell @preetapan
Add NodeName to the alloc/job status outputs.
2da173c 
Currently when operators need to log onto a machine where an alloc
is running they will need to perform both an alloc/job status
call and then a call to discover the node name from the node list.

This updates both the job status and alloc status output to include
the node name within the information to make operator use easier.

Closes #2359
Cloess #1180
preetapan pushed a commit that referenced this issue Apr 10, 2019
@jrasell @preetapan
Add NodeName to the alloc/job status outputs.
ee92bf8 
Currently when operators need to log onto a machine where an alloc
is running they will need to perform both an alloc/job status
call and then a call to discover the node name from the node list.

This updates both the job status and alloc status output to include
the node name within the information to make operator use easier.

Closes #2359
Cloess #1180
@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 Nov 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
stage/thinking theme/cli type/enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@camerondavison @dadgar @tantra35 @arshjohar @ketzacoatl @salkin