Chef Error while bootstrapping. Authorization Error: (HTTP 403)

chef-infra
Shivam Bajpai picture Shivam Bajpai · Nov 24, 2014 · Viewed 11.3k times · Source

I recreated a node with the same name. I've run into this error setting up a node and bootstrapping it:

 Starting Chef Client, version 11.16.4
 [2014-11-24T18:51:13+00:00] INFO: *** Chef 11.16.4 ***
 [2014-11-24T18:51:13+00:00] INFO: Chef-client pid: 4540
 Creating a new client identity for node1 using the validator key.
 [2014-11-24T18:51:15+00:00] INFO: Client key /etc/chef/client.pem is not present - registering
 [2014-11-24T18:51:16+00:00] INFO: HTTP Request Returned 409 Conflict: Client already exists
 [2014-11-24T18:51:16+00:00] INFO: HTTP Request Returned 403 Forbidden: error

 ================================================================================
 Chef encountered an error attempting to create the client "node1"
 ================================================================================


 Authorization Error:
 --------------------
 Your validation client is not authorized to create the client for this node (HTTP 403).



 Possible Causes:
 ----------------
 * There may already be a client named "node1"

 * Your validation client (chef-validator) may have misconfigured authorization permissions.

Answer

Shivam Bajpai picture Shivam Bajpai · Nov 24, 2014

In this situation I did not delete the client. The node was recreated with the same name so the node and client both needed to be deleted. Here are the commands to do so.

knife node delete <node-name>
knife client delete <node-name>

In the above situation it must be:

knife node delete node1
knife client delete node1

Related questions

How to move/copy files locally with Chef

I haven't yet come across a Chef resource that will copy/move files locally. For example, I want to download jetty hightide and unzip it. Once done, copy all the files into a particular folder, like this: # mv /var/tmp/…

Read More
Overriding attributes in the recipe

Let's say I have a default attribute in a cookbook: default.nginx_upstreams = { 'service1' => ['service1.server.com'], 'service2' => ['service2.server.com'], } Then it gets modified and overridden in roles and environments until it finally gets to …

Read More
Which special characters need escaping in a solr query?

Update: I think this question has to do with solr syntax in general, and not Chef in particular. So while I ran into this working with Chef, I presume that anyone working with Solr will also experience this... I'm working …

Read More