Having problems with deploying micro on a group Expected(200) <=> Actual(400 Bad Request) (Excon::Errors::BadRequest)

[Michael]

Hi I am having a problems installing an app with rubber gives me: Expected(200) <=> Actual(400 Bad Request) (Excon::Errors::BadRequest)

Below is a link to the entire failure message in terminal

http://pastie.org/7941757

[Michael]

I forgot to give the rubber.yml file 

Can you guys see if i am inputting any of the information incorrectly?

http://pastie.org/7942209

Its giving a 400 bad request meaning the html syntax that is being passed to ec2 is wrong

[Nic Barthelemy]

I'm having exactly the same problem.  I've tried different AMIs and sizes, different roles, re-vulcanizing etc.  The problem occurs 90% of the time on almost any fog call (assign static etc.).  Once in a great while things work.  No rhyme or reason...

I thought it was because I was running in a VM and I had a time sync problem.  Nope.  I tried things on a regular machine, and checked the clock.  No issue.

I've got a machine that is down at the moment, and will probably roll back to get it up again.

Help!

Nic

[Michael]

Thank god i am not the only one facing this issue. This is really frustrating i even created a ubuntu vm to test if it was my osx that was acting up.

Your using the same exact configs as before? so is this issue more to do with amazon or rubber?

[Kevin Menard]

Hi guys,

I just released rubber 2.4.0.  I really doubt anything in there will fix your problem, but during testing I found that since Excon 0.22.0 was released, Excon suppresses error messages.  If you want help tracking down your problem, I suggest locking down fog & excon in your Gemfile.  Then you should get some useful info in the error message.

-- 

Kevin

--
You received this message because you are subscribed to the Google Groups "rubber" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubber-ec2+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[skwasha]

I've no idea if this is exactly your problem or not... But I was running into the same thing. I still don't know *why* this was causing the error, only that it was - I was trying to designate my availability_zone as us-east-1c. If I changed to a different zone, no problems. But for whatever reason, us-east-1c yielded that same error.

[Michael]

Yeah that worked. In my rubber.yml i uncommented the #availability_zone: default put it at availability_zone: us-east-1b I noticed if i used us-east-1a the zone would automatically give the error 

[Shyam Visamsetty]

i still see the problem even with using us-east-1b. Any other pointers?

[Kevin Menard]

If you leave the availability_zone blank, Amazon should pick on that works.  Are you seeing otherwise?

 

--

Kevin

[Shyam Visamsetty]

Hi Kevin,

I think it is not related to any Amazon availability zone. I downgraded my excon version from 0.22.01 to 0.21.0

Adding this in the gem file and then bundle, fixed the problem.

gem 'excon', '~> 0.21.0'

I am not aware of the root cause though.

Thanks,

Shyam