Thanks Daniel. Yes the server URL is the format difference I was talking about.
From: Daniel DeLeo [mailto:email@example.com] On Behalf Of Daniel DeLeo
Sent: Wednesday, December 03, 2014 4:18 PM
Subject: [chef] Re: RE: chef server 12 issues (Sorry, I can’t find what you are looking for)
On Wednesday, December 3, 2014 at 12:57 PM, Fouts, Chris wrote:
Did you update your *.pem files and knife.rb to make your chef workstation compatible with your Chef 12 server? The format is totally different.
pem files and knife.rb should generally be the same. What is different is that you have multi-tennancy, which means you need to create an organization and reference it in your chef_server_url, e.g. it should look like https://chef-server.example/organizations/ORGNAME/
From: Eric Swenson [mailto:firstname.lastname@example.org]
Sent: Wednesday, December 03, 2014 3:51 PM
To: email@example.com (mailto:firstname.lastname@example.org)
Subject: [chef] chef server 12 issues (Sorry, I can’t find what you are looking for)
I have been successfully using Chef with a non-hosted Chef Server for quite some time. I recently installed a new Chef Server 12 server and the latest ChefDK. Now, I’m unable to use the “knife cookbook upload” command to upload cookbooks to the new Chef server. Knife displays the HTML (ugh) response from the server, which includes the 404 HTTP status code and helpful message: Sorry, I can’t find what you are look for.
In fact, the server appears to return 404 for lots of knife commands (e.g. “knife role list”, “knife role create ROLE”, “knife cookbook list”, “knife client list”, etc.). It appears to work fine for “knife user show USER” (returning my user entry) and appears to be access checking fine, for commands like “knife user list”, which tells me I’m not the pivotal user. But why is it not allowing me to create roles and upload cookbooks, etc?
I’d like to not have to revert to Chef 11.
Note: I installed the bare (no premium features) of Chef Server 12. As far as I can tell, this is all that should be required.