mitchellh/vagrant-aws

Vagrant 1.8.1 hangs at SSH

pascalwacker opened this issue · 1 comments

Hi I tried to start a EC2 instance, which kind of works (it is created in the AWS control pannel and it is up and running). But unfortunately it can't establish an ssh connection.

My Vagrant version is 1.8.1, running on an Ubuntu 15.10 64bit machine. The Vagrant file was created, using https://puphpet.com/

I suspect, that Amazon changed the event/notification for when ssh is ready.

Console output

pascal@Lenovo2013:~/VM/amazon/foobar$ sudo vagrant up
Bringing machine 'aws' up with 'aws' provider...
/home/pascal/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/run_instance.rb:98: warning: duplicated key at line 100 ignored: :associate_public_ip
==> aws: Warning! The AWS provider doesn't support any of the Vagrant
==> aws: high-level network configurations (`config.vm.network`). They
==> aws: will be silently ignored.
==> aws: Launching an instance with the following settings...
==> aws:  -- Type: m3.medium
==> aws:  -- AMI: ami-b265c7c1
==> aws:  -- Region: eu-west-1
==> aws:  -- Keypair: fooBar
==> aws:  -- Subnet ID: 
==> aws:  -- Elastic IP: 
==> aws:  -- Security Groups: ["foobar"]
==> aws:  -- Block Device Mapping: []
==> aws:  -- Terminate On Shutdown: false
==> aws:  -- Monitoring: false
==> aws:  -- EBS optimized: false
==> aws:  -- Source Destination check: 
==> aws:  -- Assigning a public IP address in a VPC: false
==> aws:  -- VPC tenancy specification: default
==> aws: Warning! Vagrant might not be able to SSH into the instance.
==> aws: Please check your security groups settings.
==> aws: Waiting for instance to become "ready"...
==> aws: Waiting for SSH to become available...

My bad, I haven't changed the ssh user to ubuntu -.-