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 1.7.7 Inconsistent Service Discovery Between UI & CLI #21339

Closed
rahadiangg opened this issue May 20, 2024 · 2 comments
Closed

Nomad 1.7.7 Inconsistent Service Discovery Between UI & CLI #21339

rahadiangg opened this issue May 20, 2024 · 2 comments
Labels

Comments

@rahadiangg
Copy link

Nomad version

Nomad v1.7.7
BuildDate 2024-04-16T19:26:43Z
Revision 0f34c85

Operating system and Environment details

Ubuntu 22.04.4 LTS
ARM64
4 Core 24GB

Issue

I have nomad job like this:

  1. Job A --> 1 Task --> 1 Allocation
  2. Job B --> 1 Task --> 3 Allocations

That task registed in service discovery with nomad provider. On the nomad UI that service pointed correctly for each allocation.

Screenshot 2024-05-20 at 20 33 13 Screenshot 2024-05-20 at 20 34 51

Hower, Whe I try to check using nomad service info <name> command, the result it's not same and inconsistent.

2024-05-20_20-38

Reproduction steps

Deploy 2 different job with registed to nomad provider service discovery

Expected Result

  1. The result from nomad service info <name> command same like in nomad UI
  2. Service have pointed to correct allocation

Actual Result

  1. Result of nomad service info <name> command inconsistent. Sometimes show the another allocations.
  2. Service have pointed to 3 allocations but there only one running allocation
@rahadiangg rahadiangg changed the title Nomad 1.7.7 Inconsistent Service Discovery Beetween UI & CLI Nomad 1.7.7 Inconsistent Service Discovery Between UI & CLI May 20, 2024
@jrasell
Copy link
Member

jrasell commented May 20, 2024

Hi @rahadiangg and thanks for raising this issue. I previously raised this within #19542, therefore I'll close this out as a duplicate.

@jrasell jrasell closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2024
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 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants