-
Notifications
You must be signed in to change notification settings - Fork 2k
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 agent does not show configured host_network
#11223
Comments
host_network
Hi @shantanugadgil, Thanks for raising this issue and providing configuration and reproduction steps. I'll try to reproduce your use case and update you on what I find. |
Hi @shantanugadgil, I just want to confirm. You are asking that this information be added. You are not saying that in some other scenario the information is available, but in your current configuration it is not available. Is that an accurate summary? -Derek |
Yes, I am asking that this information (about the host networks) be added to the output. As far as I tried, I was not able to "query" for the information using the cmd line |
ok thanks. I'll relabel this as an enhancement and add to the backlog for consideration then. Thx! |
This commit should address hashicorp#11223. Specifically it enhances the CLI in order to return two flavours (default,verbose) of the `node status` command. Signed-off-by: Alessandro De Blasis <[email protected]>
Hi there, I am wandering across the various projects looking for issues that I can contribute to. This one seemed like a good fit. Given the
while supplying the
|
Awesome. If approved, any chance of this making into 1.2.0 GA? |
Fixed in #11432 and will ship in 1.2.0-rc1. |
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. |
Nomad version
Nomad v1.1.5 (117a23d)
Operating system and Environment details
Amazon Linux 2
Issue
From a usability perspective, I couldn't find a way of listing the configured
host_network
on the client machine.Commands that I have tried (on the machine in question):
none of the above commands contain any clue about the
host_network
namedinternal
as shown belowReproduction steps
add the following in the client section of the Nomad agent:
restart the Nomad agent.
Expected Result
The
node status
or thenode status -verbose
should show the configuredhost_network
for the nodeActual Result
there is no information if this has been configured correctly or not.
Job file (if appropriate)
N/A; although the networking works as expected, there is no way to query the information before launching the job.
(job file in any case)
Nomad Server logs (if appropriate)
N/A
Nomad Client logs (if appropriate)
N/A
@angrycub @nickethier
The text was updated successfully, but these errors were encountered: