I installed the Chef push jobs client on the node using the push-jobs cookbook approach and running chef-client on the node.
next, from my workstation when i do:
knife node status node1
i get:
node1 unavailable.
I tried the following:
on the node:
i started ‘push jobs client service’ and ‘Chef Client Service’ service.
i ran : C:\opscode\push-jobs-client\bin>pushy-client
which gives me error:
ERROR: [myserver-pc] Exiting: No key returned from server; server may be using 1.x protocol. The config flag ‘allow_unencrypted’ disables encryption and allows use of 1.x server. Use with caution!
The push jobs cookbook version is the latest which is 3.2.0.
my workstation and node are windows 7 and win 2012 R2 respectively.
when executing ‘knife node list’ my node is listed and i also see the node in the chef server web interface.
You will either need to downgrade the chef push-jobs client to 1.3.4 or you will need to set:
node.default[‘push_jobs’][‘allow_unencrypted’] = 'true’
in your default attributes
I suggest downgrading though since I found the push-jobs client 2 is unstable with push-jobs server 1
you need to push the changes to the push-jobs client so they take effect
To downgrade you need to uninstall the current client and install the 1.3.4 one. Or depending on how you do the push-jobs client install you need to specify the version in your recipe default attributes and run the recipe on the client