-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Implement CLI/API feature showing actual hostnames where allocation runs. #2359
Comments
In the meantime I took a stab at a curl+jq script to make things a little easier: #!/bin/bash
set -e
ids=$(curl -s localhost:4646/v1/allocations | jq -r ".[] | select(.JobID==\"$1\") | .NodeID")
for id in $ids; do
curl -s localhost:4646/v1/nodes | jq -r ".[] | select(.ID==\"$id\") | .Name"
done |
Thanks! That will work in the meantime! |
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
We merged a PR that should display Node Name for job status and alloc status commands. Closing this one. |
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
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
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
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. |
Hi, this is a feature request.
Since killing a specific allocation which is part of the same job with multiple instances is not implemented yet (#2181) it would be good for purposes of chasing down that bad behaving allocation and killing it manually with kill -9 to add ability to both "nomad status " CLI and API to show the actual hostname where allocation runs along with other info like Node ID.
The text was updated successfully, but these errors were encountered: