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.
On Tue, Apr 2, 2013 at 7:48 PM, Maven User <
" target="_blank">
> wrote:
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 < > 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?
>>
>> On Tue, Apr 2, 2013 at 10:42 PM, Mike < > wrote:
>> > Having the same recently, even without VPC.
>> > Might be a Fog timeout.
>> >
>> >
>> > On Wednesday, April 3, 2013, Maven User wrote:
>> >>
>> >> Is anyone using this with any success?
>> >>
>> >> I'm struggling to get this to work with any regularity with a vpc.
>> >>
>> >> I keep getting these messages:
>> >>
>> >> Waiting for server...ERROR: Fog::Errors::Error: Reload failed,
>> >> Fog::Compute::AWS::Server <instance id here> went away
>> >>
>> >> Any suggestions? Totally at an end with this thing....
Archive powered by MHonArc 2.6.16.