You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client & Server: Consul v0.8.3 Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
Linux.
A fresh install of 0.8.3 in Docker (FROM consul:0.8.3 plus some customized config).
Description of the Issue (and unexpected/desired result)
consul members output is empty if used with master token. Without any token or with another valid token it shows cluster members as expected.
API call /v1/agent/members behaves in the same way.
Reproduction steps
/ # consul members
Node Address Status Type Build Protocol DC
agent@docker.local 192.168.99.100:18301 alive client 0.8.3 3 dc1
default 192.168.99.100:8301 alive server 0.8.3 3 dc1
/ # consul members -token=$CONSUL_MASTER_TOKEN
/ # consul members -token=$CONSUL_CLIENT_TOKEN
Node Address Status Type Build Protocol DC
agent@docker.local 192.168.99.100:18301 alive client 0.8.3 3 dc1
default 192.168.99.100:8301 alive server 0.8.3 3 dc1
consul version
for both Client and ServerClient & Server:
Consul v0.8.3 Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
consul info
for both Client and ServerClient & Server:
Operating system and Environment details
Linux.
A fresh install of 0.8.3 in Docker (
FROM consul:0.8.3
plus some customized config).Description of the Issue (and unexpected/desired result)
consul members
output is empty if used with master token. Without any token or with another valid token it shows cluster members as expected.API call
/v1/agent/members
behaves in the same way.Reproduction steps
ACL is configured as following (with CONSUL_MASTER_TOKEN/CONSUL_CLIENT_TOKEN replaced with actual values):
The text was updated successfully, but these errors were encountered: