Key not found: "consul_0.6.3_linux_amd64"

[MichaelKueller]

When I try to run the latest master of this cookbook I get this error. It seems that this key is not provided in consul_installation_binary.rb. Only linux-x86_64 is listed there. It still worked in version 1.4.3, when these keys were part of the attributes file

[johnbellone]

What are you trying to do?

[MichaelKueller]

I'm trying to install consul though this cookbook on debian 7. To be more specific I am running a kitchen test using vagrant and a debian 7.8 base box.

[johnbellone]

Yes, I guess I am confused with your error message. Would you be able to put the log in Gist? You should be able to run kitchen converge default-debian-79 to get an instance with Consul installing and running.

[MichaelKueller]

I assume the problem is that this node attribute "node['kernel']['machine']" contains: amd64. But this is not listed anymore. It basically is the same as x86_64.

The error is:

       Error executing action `enable` on resource 'consul_service[consul]'
       ================================================================================

       KeyError
       --------
       key not found: "consul_0.6.3_linux_amd64"

[johnbellone]

Please try again!

[MichaelKueller]

unfortunately the error still comes up.

This is what I use in my kitchen file:

---
driver:
  name: vagrant

provisioner:
  name: chef_zero

platforms:
  - name: debian-7.9
    driver:
      box_check_update: true
      platform: debian
      provision_command:
        - apt-get update

[johnbellone]

Okay!

I'll give that a try this afternoon.

Sent from my iPhone
JB

On Mar 17, 2016, at 12:09, Michael Küller notifications@github.com wrote:

unfortunately the error still comes up.

This is what I use in my kitchen file:

driver:
name: vagrant

provisioner:
name: chef_zero

platforms:

name: debian-7.9 driver: box_check_update: true platform: debian provision_command: - apt-get update
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub

[MichaelKueller]

Oh, sorry for bothering you! I just noticed my tests were referencing an older commit of you github repository, which is why the errormessage did not make sense with your current code.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.