Search code examples
ruby-on-rails-3amazon-ec2rubber

error while deploying rails app to ec2 using rubber gem `response_call': Expected(200) <=> Actual(400 Bad Request) (Excon::Errors::BadRequest)


when I do cap rubber:create_staging, I am getting the following error when rubber tries to create ec2 instance. Am I missing any configuration setting?

** Creating instance ami-eafa5883/t1.micro/elearn_production_default,elearn_production_web,elearn_production_web_tools,elearn_production_production,elearn_production_apache,elearn_production_app,elearn_production_passenger,elearn_production_collectd,elearn_production_common,elearn_production_monit,elearn_production_db,elearn_production_mysql,elearn_production_mysql_master,elearn_production_elasticsearch,elearn_production_examples,elearn_production_graphite_server,elearn_production_graphite_web,elearn_production_graylog_elasticsearch,elearn_production_graylog_mongodb,elearn_production_mongodb,elearn_production_graylog_server,elearn_production_graylog_web,elearn_production_haproxy/us-east-1b

/Users/svisamsetty/.rvm/gems/ruby-1.9.3-p429/gems/excon-0.22.1/lib/excon/middlewares/expects.rb:10:in response_call': Expected(200) <=> Actual(400 Bad Request) (Excon::Errors::BadRequest) from /Users/svisamsetty/.rvm/gems/ruby-1.9.3-p429/gems/excon-0.22.1/lib/excon/connection.rb:355:inresponse'


Solution

  • I'm having the same problem. It looks like it is covered as Issue #362 on the Rubber github page: https://github.com/rubber/rubber/issues/362