Skip to content

create_staging error #362

Closed
alonzorz opened this Issue May 28, 2013 · 5 comments

5 participants

@alonzorz

please help,
when I use cap rubber:create_staging I get the following error after the security groups syncing:

Creating instance ami-b6089bdf/c1.medium/bla2_production_default,bla2_production_web,bla2_production_web_tools,bla2_production
_production,bla2_production_apache,bla2_production_app,bla2_production_unicorn,bla2_production_nginx,bla2_production_collectd,bla2
_production_common,bla2_production_monit,bla2_production_db,bla2_production_postgresql,bla2_production_postgresql_master,bla2_prod
uction_elasticsearch,bla2_production_examples,bla2_production_graphite_server,bla2_production_graphite_web,bla2_production_graylog
_elasticsearch,bla2_production_graylog_mongodb,bla2_production_mongodb,bla2_production_graylog_server,bla2_production_graylog_web,
bla2_production_haproxy,bla2_production_passenger/us-east-1

/home/alon/.rvm/gems/ruby-1.9.3-p429/gems/excon-0.22.1/lib/excon/middlewares/expects.rb:10:in response_call': Expected(200) <=> A
ctual(400 Bad Request) (Excon::Errors::BadRequest)
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/excon-0.22.1/lib/excon/connection.rb:355:in
response'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/excon-0.22.1/lib/excon/connection.rb:249:in request'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/fog-1.11.1/lib/fog/core/connection.rb:21:in
request'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/fog-1.11.1/lib/fog/aws/compute.rb:384:in _request'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/fog-1.11.1/lib/fog/aws/compute.rb:379:in
request'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/fog-1.11.1/lib/fog/aws/requests/compute/run_instances.rb:119:in run_instan
ces'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/fog-1.11.1/lib/fog/aws/models/compute/server.rb:173:in
save'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/fog-1.11.1/lib/fog/core/collection.rb:52:in create'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/rubber-2.4.0/lib/rubber/cloud/fog.rb:30:in
create_instance'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/rubber-2.4.0/lib/rubber/thread_safe_proxy.rb:13:in method_missing'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/rubber-2.4.0/lib/rubber/recipes/rubber/instances.rb:311:in
create_instance
'
from /home/alon/.rvm/gems/ruby-1.9.3-p429/gems/rubber-2.4.0/lib/rubber/recipes/rubber/instances.rb:230:in `block (2 levels
) in create_instances'

@Zanfa
Zanfa commented May 29, 2013

Having the same issue. It happens by just following the Quick Start wiki. This problem is also talked about in this thread https://groups.google.com/forum/?fromgroups#!topic/rubber-ec2/Rk6DALp1g4w

However, for me changing the availability zones had no effect.

@HaasEffect

I'm having the same problem. Changing the availability zone does not work (changed it to eu-west-1b) for me. Any other solution for this? Having this problem since Rubber 2.4.2

@HaasEffect

Ok, here's my solution: I downgraded Excon by adding this to my gemfile:

gem 'excon', '~> 0.21.0'

After that it told me, that the ami does not exist (because it's only available for the US region). So I switched to ami-1a070f6e for EU (btw: are there any AMIs that rubber prefers?)

@ricpruss
ricpruss commented Jun 6, 2013

I have the same issue here but the real issue here is there is no indication of why something is breaking. The AMI was not in my region but now I have got one in my region but something is still breaking but no clear indication where I go next to figure out what is breaking.

@yaoquan
yaoquan commented Jun 10, 2013

Having the same issue here. @HaasEffect 's solution of downgrading excon to 0.21.0 works

@alonzorz alonzorz closed this Jun 20, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.