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

consul_acl (or Diplomat gem) misbehaving #283

Closed
st33v opened this Issue Feb 25, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@st33v
Copy link

commented Feb 25, 2016

based on the examples in the cookbook, I'm trying to create a simple ACL like this:

rules = "key git/lastcommit {policy = read}"

consul_acl 'git' do
  rules rules
  url "http://127.0.0.1:#{node['consul']['config']['ports']['http']}"
  type 'client'
  acl_name 'Git'
  auth_token node['consul']['config']['acl_master_token']
end

which results in a resource like this:

consul_acl("git") do
  action [:create]
  retries 0
  retry_delay 2
  default_guard_interpreter :default
  declared_type :consul_acl
  cookbook_name "vault_tgtcfg"
  recipe_name "_consul_anon"
  rules "key git/lastcommit {policy = read}"
  url "http://127.0.0.1:8500"
  type "client"
  acl_name "Git"
  auth_token "MASTER_TOKEN_SUPER_SECRET"
  id "git"
end

and an error:

[2016-02-25T21:48:00+00:00] ERROR: consul_acl[git] (vault_tgtcfg::_consul_anon line 17) had an error: Diplomat::UnknownStatus: status 301
[2016-02-25T21:48:02+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

so, Diplomat is seeing a redirect, which is odd. It's especially strange because I ran tcpdump like this:

sudo tcpdump -l -vvv -n tcp port 8500 -i any

and while I can use curl to get stuff from consul and I see the traffic in tcpdump, I see NOTHING on ANY interface on port 8500 when chef is allegedly trying to create the ACL.

I'm confused...

@st33v

This comment has been minimized.

Copy link
Author

commented Feb 27, 2016

ah... it's a still unresolved bug in faraday... Looks like you actually have resolved it @johnbellone and it's just sitting there in limbo.

@st33v st33v closed this Feb 27, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.