search

mwrock / kitchen-nodes

A Test Kitchen Provisioner that generates searchable Nodes.
Other
37 stars 24 forks source link

test-kitchen dependency version is too old #40

Open zedtux opened 5 years ago

zedtux commented 5 years ago

It's impossible to use the latest version of this gem:

  In Gemfile:
    test-kitchen

    kitchen-inspec was resolved to 1.1.0, which depends on
      test-kitchen (>= 1.6, < 3)

    kitchen-nodes (~> 0.9.1) was resolved to 0.9.1, which depends on
      test-kitchen (~> 1.13)

    kitchen-vagrant was resolved to 1.5.2, which depends on
      test-kitchen (>= 1.4, < 3)

Without setting a version, it installs the version 0.2.0.dev.1 which doesn't work with actual test-kitchen version.

Tcharl commented 5 years ago

It compiles if I remove the Gemfile lock.

However, the API has changed: when I execute kitchen converge with this provisionner, I have:


>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: 2 actions failed.
>>>>>>     Failed to complete #converge action: [undefined method `node_session' for #<Kitchen::Transport::Ssh::Connection:0x00007fd576e31d60>] on glusterstorage0-f-29
>>>>>>     Failed to complete #converge action: [undefined method `node_session' for #<Kitchen::Transport::Ssh::Connection:0x00007fd57bfe9158>] on glusterstorage1-f-29
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

Any Rubyist/Chefist to fix ? I'm just discovering the ecosystem (I'm from Java) and do not understand thinks so well: dependency management is one of the aspects I do not understand

zedtux commented 5 years ago

I just removed that gem and I'm using the chef_zero driver with node JSON files at test/fixtures/nodes/ and in my .kitchen.yml file I'm passing:

provisioner:
  nodes_path: test/fixtures/nodes
Tcharl commented 5 years ago

However, it constraints to have a Vagrantfile to setup the node format, which is more cumbersome than using this plugin if it were updated

zedtux commented 5 years ago

Heum, no it doesn't, I don't have any Vagrantfile in my project.

mcascone commented 5 years ago

Not sure if this is the same problem, but i get this: Message: Unable to activate kitchen-nodes-0.9.1, because test-kitchen-2.2.5 conflicts with test-kitchen (~> 1.13)

I am on chef v15:

ChefDK version: 4.3.13
Chef Infra Client version: 15.2.20
Chef InSpec version: 4.10.4
Test Kitchen version: 2.2.5
Foodcritic version: 16.1.1
zedtux commented 5 years ago

@mcascone you seem to have the same issue as me.

webframp commented 5 years ago

Seeing some related issues. Are there plans to update this or keep it maintained? I'd be happy to send a PR with fixes if it's desired

scalp42 commented 5 years ago

please do @webframp !

mcascone commented 5 years ago

a fork of kitchen-nodes seems to fix this. See #29, #20, and https://rubygems.org/gems/kitchen-nodes-scalp42