tobami / littlechef

Cook with Chef without a Chef Server
Apache License 2.0
472 stars 71 forks source link

littlechef does not horning autodeploy_chef set in littlechef.cfg #249

Open wilddog64 opened 8 years ago

wilddog64 commented 8 years ago

The current version 1.8.0 does not horning what specific in README document for

[userinfo]
autodeploy_chef=true

if set to true, a check will be performed before each deployment for chef-solo, and if it is not present it will be installed using the omnibus method.

Here's my setting at my project littlechef.cfg:

[userinfo] user = ec2-user password = keypair-file = /Users/chengkai.liang/.ssh/dblOps.pem ssh-config = /Users/chengkai.liang/.ssh/config encrypted_data_bag_secret = autodeploy_chef=true

[kitchen] node_work_path = /tmp/chef-solo/ berksfile = Berksfile berksfile_cookbooks_directory = cookbooks

now running command,

fix node:ec2-54-227-11-220.compute-1.amazonaws.com recipe:dbl_nginx

does not triggering chef-solo installation

Vendoring cookbooks from Berksfile Berksfile to directory cookbooks...

== Applying recipe 'dbl_nginx' on node ec2-54-227-11-220.compute-1.amazonaws.com == Creating new node file 'ec2-54-227-11-220.compute-1.amazonaws.com.json'

Warning: sudo() received nonzero return code 127 while executing '/usr/bin/ohai -l warn ipaddress'!

Saving node configuration to nodes/ec2-54-227-11-220.compute-1.amazonaws.com.json... Synchronizing nodes, environments, roles, cookbooks and data bags... Warning: Permanently added 'ec2-54-227-11-220.compute-1.amazonaws.com' (RSA) to the list of known hosts.

Cooking... /bin/bash: /usr/bin/chef-solo: No such file or directory

FAILED: chef-solo could not finish configuring the node