{"action":"closed","issue":{"url":"https://api.github.com/repos/hashicorp/vault/issues/178","labels_url":"https://api.github.com/repos/hashicorp/vault/issues/178/labels{/name}","comments_url":"https://api.github.com/repos/hashicorp/vault/issues/178/comments","events_url":"https://api.github.com/repos/hashicorp/vault/issues/178/events","html_url":"https://github.com/hashicorp/vault/issues/178","id":74489672,"number":178,"title":"HA mode not showing proper leader in CLI output","user":{"login":"jefferai","id":28627,"avatar_url":"https://avatars.githubusercontent.com/u/28627?v=3","gravatar_id":"","url":"https://api.github.com/users/jefferai","html_url":"https://github.com/jefferai","followers_url":"https://api.github.com/users/jefferai/followers","following_url":"https://api.github.com/users/jefferai/following{/other_user}","gists_url":"https://api.github.com/users/jefferai/gists{/gist_id}","starred_url":"https://api.github.com/users/jefferai/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jefferai/subscriptions","organizations_url":"https://api.github.com/users/jefferai/orgs","repos_url":"https://api.github.com/users/jefferai/repos","events_url":"https://api.github.com/users/jefferai/events{/privacy}","received_events_url":"https://api.github.com/users/jefferai/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/hashicorp/vault/labels/bug","name":"bug","color":"f7c6c7"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-05-08T20:45:33Z","updated_at":"2015-05-11T17:54:32Z","closed_at":"2015-05-11T17:54:32Z","body":"I'm trying to use HA mode, but all nodes remain in standby. I am using a Consul backend, and all Vault instances are unsealed and have `advertise_addr` properly configured; I can curl against the various addresses successfully.\r\n\r\nHowever, all three nodes report no leader and on standby:\r\n```\r\n$ vault status\r\nSealed: false\r\nKey Shares: 5\r\nKey Threshold: 2\r\nUnseal Progress: 0\r\n\r\nHigh-Availability Enabled: true\r\n\tMode: standby\r\n\tLeader: <none>\r\n```\r\nIn the logs for all three I get this:\r\n```\r\n2015/05/08 20:37:04 [ERR] core: failed to acquire lock: failed to acquire lock: Unexpected response code: 403 (rpc error: Permission denied)\r\n```\r\nThis suggests one of two things, to me:\r\n\r\n1. This RPC error originates from Consul, and Vault is not using my provided ACL token (although it is successfully using it during startup and unsealing)\r\n2. This is an RPC error between Vault nodes, and something is required for me to grant access, but I have no idea what\r\n\r\nMy config looks like the following:\r\n```\r\nbackend \"consul\" {\r\n    scheme = \"http\"\r\n    token = \"[redacted]\"\r\n    advertise_addr=\"http://10.88.0.1:8200\"\r\n}\r\n\r\nlistener \"tcp\" {\r\n    address = \"0.0.0.0:8200\"\r\n    tls_disable = 1\r\n}\r\n```"}}