[chef] Re: Why does knife sometime decide to bomb out?

[Daniel DeLeo < >]

On Monday, April 16, 2012 at 9:22 PM, David Montgomery wrote:

> Hi,
> 
> Per the below....this happens about 10% of the time. Why does this
> happen? This just happened three times in a row.
> 
> 
 :~/.chef$
>  knife ec2 server create -r
> "role[monitor_server]" -E development --region ap-southeast-1 -Z
> ap-southeast-1a -I ami-c4622596 --flavor m1.medium -G nginx -x ubuntu
> -S sg_development -i /home/ubuntu/.ec2/sg_development.pem
> Instance ID: i-ba8a5dee
> Flavor: m1.medium
> Image: ami-c4622596
> Region: ap-southeast-1
> Availability Zone: ap-southeast-1a
> Security Groups: nginx
> SSH Key: sg_development
> 
> Waiting for server..............
> Public DNS Name: ec2-46-137-237-153.ap-southeast-1.compute.amazonaws.com 
> (http://ec2-46-137-237-153.ap-southeast-1.compute.amazonaws.com)
> Public IP Address: 46.137.237.153
> Private DNS Name: ip-10-131-34-124.ap-southeast-1.compute.internal
> Private IP Address: 10.131.34.124
> 
> Waiting for sshd.done
> Bootstrapping Chef on 
> ec2-46-137-237-153.ap-southeast-1.compute.amazonaws.com 
> (http://ec2-46-137-237-153.ap-southeast-1.compute.amazonaws.com)
> ERROR: Net::SSH::HostKeyMismatch: fingerprint
> f2:50:06:7a:7c:dc:e3:94:08:89:a4:ae:04:3c:ab:a9 does not match for
> "ec2-46-137-237-153.ap-southeast-1.compute.amazonaws.com 
> (http://ec2-46-137-237-153.ap-southeast-1.compute.amazonaws.com),46.137.237.153"

It's exactly what it says. SSH strict host key checking is enabled, and you 
have a different fingerprint for this IP/hostname in your known_hosts file.

-- 
Dan DeLeo