On 7 May 2015, at 11:13 am, Daniel DeLeo dan@kallistec.com wrote:
I don't think there's a bug. Just user error. I finally figured it out.
Glad to hear.
As an aside: is there a way to do bootstrap from knife in local mode?
Chef Provisioning can create machines from local mode but knife does not have this ability.
I’m having the same issue - but I’m using chef-provisioning for bootstrap. It only fails when the chef zero socketless mode is tried to be used by the client on each node.
- [cheffrontendTEST1.int] update node cheffrontendTEST1.int at chefzero://localhost:8889
- [cheffrontendTEST1.int] add normal.aws_ha_chef = {:aws_access_key_id=>”x", :aws_secret_access_key=>”y", :backend1=>{:fqdn=>”chefbackendTEST1.int", :ip_address=>"172.21.1.85"}, :backend2=>{:fqdn=>”chefbackendTEST2.int", :ip_address=>"172.21.1.86"}, :frontends=>{:fe1=>{:fqdn=>”cheffrontendTEST1.int", :ip_address=>"172.21.1.88"}, :fe2=>{:fqdn=>”cheffrontendTEST2.int", :ip_address=>"172.21.1.111"}}}
- [cheffrontendTEST1.int] remove normal.aws_ha_chef[2015-05-18T17:04:41+10:00] INFO: Converging cheffrontendTEST1.int because the resource was updated ...
[2015-05-18T17:04:41+10:00] INFO: Port forwarded: local URL chefzero://localhost:8889 is available to 172.21.1.88 as chefzero://localhost:8889 for the duration of this SSH connection.
[2015-05-18T17:04:41+10:00] INFO: Executing sudo chef-client -l info on ubuntu@172.21.1.88
[cheffrontendTEST1.int] [2015-05-18T07:04:41+00:00] INFO: Forking chef instance to converge...
Starting Chef Client, version 12.3.0
[2015-05-18T07:04:41+00:00] INFO: *** Chef 12.3.0 ***
[2015-05-18T07:04:41+00:00] INFO: Chef-client pid: 1505
================================================================================
Chef encountered an error attempting to load the node data for “cheffrontendTEST1.int"
================================================================================
Unexpected Error:
-----------------
ChefZero::ServerNotFound: No socketless chef-zero server on given port 8889
[2015-05-18T07:04:42+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 0.859637226 seconds
[2015-05-18T07:04:42+00:00] ERROR: No socketless chef-zero server on given port 8889
[2015-05-18T07:04:42+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
[2015-05-18T17:04:42+10:00] INFO: Completed chef-client -l info on ubuntu@172.21.1.88: exit status 1
Using chefDK 0.6.0 and client 12.3 as well.
$ chef gem list |grep chef
chef (12.3.0)
chef-dk (0.6.0)
chef-provisioning (1.1.1)
chef-provisioning-aws (1.1.1)
chef-provisioning-azure (0.3.2)
chef-provisioning-fog (0.13.2)
chef-provisioning-vagrant (0.8.3)
chef-vault (2.4.0)
chef-zero (4.2.1, 1.5.6)
cheffish (1.2)
chefspec (4.2.0)
#knife.rb
log_level :info
log_location STDOUT
node_name 'bootstrap'
client_key '/Users/ted/chef/.chef/bootstrap.pem'
validation_client_name 'bootstrap'
#chef_server_url 'http://localhost:8889'
validation_key '/Users/ted/chef/.chef/keys/bootstrap.pem'
syntax_check_cache_path '/Users/ted/chef/.chef/syntax_check_cache'
cookbook_path [ '~/chef/cookbooks', '~/chef/berks-cookbooks' ]
knife[:aws_access_key_id] = “x"
knife[:aws_secret_access_key] = “y"
knife[:region] = "ap-southeast-2”
It’s been driving me crazy all day.
Before ChefDK 0.6.0 and Client 12.3 I used to instantiate a local chef-zero server and it would bootstrap fine.
I’ve even tried the —no-listen option; but no luck.
Not sure if it’s a bug in chef-provisioing-aws, but I might raise an issue over with them too.
(I do have a forward slash in my secret access key - which I’ve read somewhere can be an issue, but chef-provisioning is bootstrapping OK; just client runs failing)
--
Ted
GPG Key: 0x2B272DFD | E564 BCC1 F601 5D1F 01CD AC10 C37D D2B0 2B27 2DFD