Since that check is currently doing a naive port check, it will fail for clients using nonstandard ssh ports or ssh proxies. I added a new parameter to replace the check with a delay so folks can work around this for now. I may also look at patching chef to add a new function to do a real ssh test, so knife-ec2 can just use that.
Adding a parameter to the server create call to allow skipping the ss…
…hd check. Since that check is currently doing a naive port check, it will fail for clients using nonstandard ssh ports or ssh proxies.
Apologies for the delay. I believe that the --ssh-port option committed here:38efc40 addresses at least a portion of your concerns.
If you still think that this feature is worthwhile, can you open an issue at http://tickets.opscode.com and attach a link to your branch? We will also need to ensure you've completed a Contributor License Agreement (CLA). Please take a moment to review the below wiki page for the appropriate steps:
Closing this ticket for gardening purposes, but please see my message above on the next steps if you still have concerns. Thanks for helping to make Chef better!
Thanks for taking a look at this. This isn't super high on my list right now since we have a workaround, but the issue we ran into wasn't the port, but that we're using a proxy (behind our firewall) to connect to aws, so connecting to the machine directly doesn't work, which is what knife ec2 is trying to do here.