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 0.6.2 breaks status for jobs with dash in name #3155

Closed
tino opened this issue Sep 3, 2017 · 2 comments
Closed

Nomad 0.6.2 breaks status for jobs with dash in name #3155

tino opened this issue Sep 3, 2017 · 2 comments

Comments

@tino
Copy link

tino commented Sep 3, 2017

This works in 0.6.0. Also find it strange that it tries to search for an alloc, as that is what alloc-status is for right?

Nomad version

Nomad v0.6.2

Operating system and Environment details

Mac OS X Sierra; Ubuntu

Issue

$ nomad status app-production
Error querying search with id: "Unexpected response code: 500 (3 error(s) occurred:\n\n* RPC failed to server 10.0.0.49:4647: rpc error: alloc lookup failed: index error: Input (without hyphens) must be even length\n* RPC failed to server 10.0.0.12:4647: rpc error: alloc lookup failed: index error: Input (without hyphens) must be even length\n* RPC failed to server 10.0.0.19:4647: rpc error: alloc lookup failed: index error: Input (without hyphens) must be even length)"

Job file (if appropriate)

job "app-production" {
   ...
@dadgar
Copy link
Contributor

dadgar commented Sep 3, 2017

Hey this is a duplicate of #3118. It will be fixed in 0.6.3. Also status is now a general purpose command that can route to the appropriate status of any Nomad object. You can use nomad job status instead if you just want jobs.

@dadgar dadgar closed this as completed Sep 3, 2017
@github-actions
Copy link

github-actions bot commented Dec 8, 2022

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 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants