Knife-ec2 and fog use the same EC2 API end points that the Amazon-provided EC2 tools use, so there's a chance that the latter will fail as well. I second the idea of testing provisioning manually and bootstrapping, at least if you are in a bind.
I've spent weeks building up this process around the knife plugin and
tonight for whatever reason, things have gotten uber flaky.
I think I'm going to have to redo all of this using the EC2 tools.....
On Tue, Apr 2, 2013 at 10:45 PM, Mike miketheman@gmail.com wrote:
You can also use EC2 API tools to launch instances and then use knife
bootstrap.
On Wednesday, April 3, 2013, Maven User wrote:
time out and/or retry.
Anyone else?
Is there an alternative to the ec2 plugin and/or fog?
im using the plugin both with and without VPC, and without any trouble.
Certain stuff dont work in vpc mode (like security groups can not be
referred by name etc). Are you recently getting these errors? or you are
just trying them afresh? From your error it looks like a fog related issue.
Can you share the full stack trace with -VV ?
Knife-ec2 and fog use the same EC2 API end points that the Amazon-provided
EC2 tools use, so there's a chance that the latter will fail as well. I
second the idea of testing provisioning manually and bootstrapping, at
least if you are in a bind.
im using the plugin both with and without VPC, and without any trouble.
Certain stuff dont work in vpc mode (like security groups can not be
referred by name etc). Are you recently getting these errors? or you are
just trying them afresh? From your error it looks like a fog related issue.
Can you share the full stack trace with -VV ?
Knife-ec2 and fog use the same EC2 API end points that the Amazon-provided
EC2 tools use, so there's a chance that the latter will fail as well. I
second the idea of testing provisioning manually and bootstrapping, at least
if you are in a bind.
Chiming in with another data point. I've used the knife ec2 plugin for a
year and a half and it's never given me any problems. If it's an
intermittent problem it's likely that the ec2 endpoints are timing out on
you, or that the version of the fog gem that underlies the knife-ec2 plugin
has a brand new bug in it.
If it's the ec2 endpoint timing out on you, then the ec2 command line tools
won't work. If it's fog, then they will. You can test fog in IRB, or just
see if it's had a recent release and downgrade it via your Gemfile.
im using the plugin both with and without VPC, and without any trouble.
Certain stuff dont work in vpc mode (like security groups can not be
referred by name etc). Are you recently getting these errors? or you are
just trying them afresh? From your error it looks like a fog related
issue.
Can you share the full stack trace with -VV ?
Knife-ec2 and fog use the same EC2 API end points that the
Amazon-provided
EC2 tools use, so there's a chance that the latter will fail as well. I
second the idea of testing provisioning manually and bootstrapping, at
least
if you are in a bind.