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

Agent service address field only visible for local services #658

Closed
sttts opened this issue Jan 29, 2015 · 1 comment
Closed

Agent service address field only visible for local services #658

sttts opened this issue Jan 29, 2015 · 1 comment

Comments

@sttts
Copy link
Contributor

sttts commented Jan 29, 2015

The address field – introduced in #570 – is only correctly returned via the API for services on the local host.

As an example I have three mongo instances on three different hosts (each running a consul server instance). On each host I get a different picture from /v1/agent/services:

[
  {
    "Port": 27017,
    "Address": "",
    "Tags": [
      "tweventy"
    ],
    "Service": "mongo",
    "ID": "master2:mesos-7095bd12-e725-41cf-a664-28d0b5e8ffca:27017"
  },
  {
    "Port": 27017,
    "Address": "10.2.0.9",
    "Tags": [
      "tweventy"
    ],
    "Service": "mongo",
    "ID": "master2:mesos-8527777f-3fa7-4602-b0b5-a844698c3881:27017"
  },
  {
    "Port": 27017,
    "Address": "",
    "Tags": [
      "tweventy"
    ],
    "Service": "mongo",
    "ID": "master2:mesos-883a2b28-a82f-43a5-b625-08a544d9f817:27017"
  }
]

On host1 only the service on host1 has a filled address field, on host2 only the service on host2 and so on.

@sttts
Copy link
Contributor Author

sttts commented Jan 29, 2015

False alarm.

@sttts sttts closed this as completed Jan 29, 2015
duckhan pushed a commit to duckhan/consul that referenced this issue Oct 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant