I successfully bootstrapped my node, which run an empty run list knife bootstrap node_name -N node_name -E my_env -x root -P password Connecting to
node_name Node_name Starting first Chef Client run... Node_name [2014-11-05T13:22:04-05:00] WARN: Node_name * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * Node_name SSL validation of HTTPS requests is disabled. HTTPS connections
are still Node_name encrypted, but chef is not able to detect forged replies
or man in the middle Node_name attacks. Node_name To fix this issue add an entry like this to your configuration
file: Node_name ``` Node_name # Verify all HTTPS connections (recommended) Node_name ssl_verify_mode :verify_peer Node_name # OR, Verify only connections to chef-server Node_name verify_api_cert true Node_name ``` Node_name To check your SSL configuration, or troubleshoot errors,
you can use the Node_name `knife ssl check` command like so: Node_name ``` Node_name knife ssl check -c /etc/chef/client.rb Node_name ``` Node_name Node_name * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * Node_name Starting Chef Client, version 11.12.2 Node_name Creating a new client identity for node_name using the validator
key. Node_name resolving cookbooks for run list: [] Node_name Synchronizing Cookbooks: Node_name Compiling Cookbooks... Node_name [2014-11-05T13:22:07-05:00] WARN: Node node_name has an empty
run list. Node_name Converging 0 resources Node_name Running handlers: Node_name Running handlers complete Node_name Chef Client finished, 0/0 resources updated in 2.479062 seconds knife node show node_name Node Name:
node_name Environment: my_env FQDN: node_name IP: <removed> Run List:
Roles: Recipes: Platform: redhat 5.11 Tags: knife ssh "name:node_name" "pwd" -x root -P password FATAL: No nodes returned from search! I CAN go to the node, node_name, and run chef-client from it. I’ve done the process repeatedly to no avail. Why? How can I fix it? Chris |
Archive powered by MHonArc 2.6.16.