Closed mickfeech closed 9 years ago
According to
[2015-11-04T09:32:12-05:00] DEBUG: Initiating POST to https://server1/organizations/my_org/clients
[2015-11-04T09:32:12-05:00] DEBUG: ---- HTTP Request Header Data: ----
[2015-11-04T09:32:12-05:00] DEBUG: Content-Type: application/json
[2015-11-04T09:32:12-05:00] DEBUG: Accept: application/json
[2015-11-04T09:32:12-05:00] DEBUG: Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
[2015-11-04T09:32:12-05:00] DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
[2015-11-04T09:32:12-05:00] DEBUG: X-OPS-USERID: server1
[2015-11-04T09:32:12-05:00] DEBUG: X-OPS-TIMESTAMP: 2015-11-04T14:32:12Z
<...>
[2015-11-04T09:32:12-05:00] DEBUG: Content-Length: 586
[2015-11-04T09:32:12-05:00] DEBUG: ---- End HTTP Request Header Data ----
[2015-11-04T09:32:12-05:00] DEBUG: ---- HTTP Status and Header Data: ----
[2015-11-04T09:32:12-05:00] DEBUG: HTTP 1.1 403 Forbidden
<...>
[2015-11-04T09:32:12-05:00] DEBUG: ---- HTTP Response Body ----
[2015-11-04T09:32:12-05:00] DEBUG: {"error":["missing create permission"]}
[2015-11-04T09:32:12-05:00] DEBUG: ---- End HTTP Response Body -----
[2015-11-04T09:32:12-05:00] DEBUG: ---- HTTP Request Body ----
[2015-11-04T09:32:12-05:00] DEBUG: {"name":"app.myapp.local","clientname":"app.myapp.local","admin":false,"validator":false,"chef_type":"client","public_key":"-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyMY98wd6iTOBiCxOYfNe\nO/Q+Q8t2e0Iv/GLiBunvRxirsIP2gsTUNbtYaOvUJP6A4nWpv2b7XJXczxVBw9nl\neQKB6qb4t9FIxZaElH7wzp5+74RQkl7jPvkh9qcWZBWcNCa5kRaPEif9unKqG6NM\nS4OhDFdxt6tXqMlVXhk8/PLFXY7/G7Y5JE+k9DqxgpiQFbBeeCjTcQJr6MHvt/Cl\nNh8T3hy2BqQCJyssBSvSIsJfhfc9XNEkcohq3LhBbGyojGWXA9LlUjphGIv010QY\nXP6gCpXD/sTCegbnGdeplUyi62gZZSLcgSNPr5UqTXZVGY0oW+0Fa1JnnV9BEbGx\n/wIDAQAB\n-----END PUBLIC KEY-----\n"}
[2015-11-04T09:32:12-05:00] DEBUG: ---- End HTTP Request Body ----
it seem your user doesn't have enough permissions to create new client on chef server. I would take a look at http://jtimberman.housepub.org/blog/2015/02/09/quick-tip-create-a-provisioner-node/ .
Thanks. It would have been nice to see that in the chef documentation.
I've been receiving very similar messages that have been experienced with provisioning to aws (https://github.com/chef/chef-provisioning/issues/469) trying to provision to docker.