The issue and this behavior is tracked here: https://github.com/mitchellh/vagrant-aws/issues/240
Il giorno giovedì 22 agosto 2013 02:47:38 UTC+2, Inny So ha scritto: > > In case if anyone is having the same issue, i found out the problem was > because I used group name instead of group id. > > cheers > > On Wednesday, August 14, 2013 11:23:46 PM UTC+10, Inny So wrote: > >> Hi All, >> >> Does anyone have example for vagrant-aws with vpc. I am having issue with >> creating an instance on vpc. My vagrant file works on the classic instance >> but not vpc. I created a new vpc and the corresponding subnet already. I >> added the following in the Vagrant file: >> >> aws.subnet_id = "..." >> aws.elastic_ip=true >> >> and when i tried to do vagrant up, it just stuck in the Security Group >> for a while and then i got the following error: >> >> INFO interface: info: -- Security Groups: ["vagrant"] >> [default] -- Security Groups: ["vagrant"] >> ERROR warden: Error occurred: connect timeout reached >> INFO warden: Beginning recovery process... >> INFO warden: Calling recover: >> #<VagrantPlugins::AWS::Action::RunInstance:0x00000100b79f98> >> INFO machine: Calling action: read_state on provider AWS (new) >> INFO runner: Running action: #<Vagrant::Action::Builder:0x00000101574930> >> INFO warden: Calling action: >> #<Vagrant::Action::Builtin::ConfigValidate:0x00000101573580> >> INFO warden: Calling action: >> #<VagrantPlugins::AWS::Action::ConnectAWS:0x00000101573558> >> INFO connect_aws: Connecting to AWS... >> INFO warden: Calling action: >> #<VagrantPlugins::AWS::Action::ReadState:0x00000100ac18f8> >> INFO warden: Recovery complete. >> INFO warden: Beginning recovery process... >> INFO warden: Recovery complete. >> INFO warden: Beginning recovery process... >> INFO warden: Recovery complete. >> INFO warden: Beginning recovery process... >> INFO warden: Recovery complete. >> ERROR warden: Error occurred: connect timeout reached >> INFO warden: Beginning recovery process... >> INFO warden: Calling recover: >> #<Vagrant::Action::Builtin::Call:0x0000010214d590> >> INFO warden: Beginning recovery process... >> INFO warden: Recovery complete. >> INFO warden: Recovery complete. >> INFO warden: Beginning recovery process... >> INFO warden: Recovery complete. >> INFO warden: Beginning recovery process... >> INFO warden: Recovery complete. >> INFO environment: Running hook: environment_unload >> INFO runner: Running action: #<Vagrant::Action::Builder:0x0000010098d0e0> >> /Users/xxx/.vagrant.d/gems/gems/excon-0.25.3/lib/excon/socket.rb:177:in >> `rescue in block in connect': connect timeout reached >> (Excon::Errors::Timeout) >> >> Any help would be greatly appreciate. >> >> Thank you very much. >> >> cheers, >> inny >> >> -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
