Chef Server (First 5 Nodes Free)
Progress Chef | 12.8.0-2Linux/Unix, CentOS 7.2 - 64-bit Amazon Machine Image (AMI)
Broken SSH keys
SSH key specified in launch sequence does not work.
Initial user key does not work
reset user key does not work.
This is after 3 scrubbed servers and three from scratch starts.
Each time before going to the web interface I tried the initial ssh key. Didn't work.
Since the majority of reviews here were unfavorable, I have to ask myself why I tried the product. I didn't believe it either, but this product is not market ready.
- Leave a Comment |
- Mark review as helpful
Worked once, then not again
Same issues that others are experiencing, cannot get it to work, internal 500 error, then after upgrading cannot log in.
Good to start with Chef
We have no problemas to configure the fqdn to access the ec2-instances. We have assined a fixed public ip.
Before you start using the https://fqdn, you must to log in in EC2 and do a chef-server-ctl reconfigure
Doesn't work
Before you tell me how to make it work, let me ask you why the documentation doesn't include those instructions? I followed it to a T and cannot connect. I've used chef server in the past, set it up myself and it worked fine. This AMI, not so much.
No, it isn't the security group (used yours).
No, it isn't the version (upgraded).
The whole point of an AMI is simplicity. It should just work with minimal configuration.
I am disappointed
I am not sure this is a production ready tested product. Changing the FQDN to elastic IP never works even following the instructions below and it gives you 500 internal server error when you upload the cookbook. To make thing worst there is no consistency because knife ssl fetch and knife client list runs successfully after the FQDN changes. When you download the chef starter kit from the Chef GUI it is also extremely buggy and don't recognize the FQDN changes in the downloaded knife.rb file and shows you the old IP in the server URL.
Run sudo -i to gain administrator privileges.
Run chef-marketplace-ctl hostname to view the current hostname.
Configure the api_fqdn in /etc/chef-marketplace/marketplace.rb
$ echo 'api_fqdn "
Run chef-server-ctl stop to stop Chef server.
Run chef-marketplace-ctl hostname
Run chef-server-ctl reconfigure to ensure Chef server has beeen correctly configured with the new hostname.
Run chef-server-ctl restart to restart Chef server