No route to host - connect(2) for "169.254.169.254" port 80 when using aws_s3_file resource

585 views
Skip to first unread message

Roger Micone

unread,
Aug 19, 2015, 3:00:11 PM8/19/15
to Vagrant
I can't reproduce this on my own machine, but one of the users who tried to use my cookbook and Vagrantfile reported this issue

I'm using aws cookbook 2.7.2 so I'm thinking it could be that too... I will post to their git issues and see if there's something up.

==> app: ================================================================================
==> app:     
==> app: Error executing action `create` on resource 'aws_s3_file[/root/tmp/collab-server-master_v9.zip]'
==> app:     
==> app: ================================================================================
==> app:     
==> app: 
==> app: 
==> app:     
==> app: Errno::EHOSTUNREACH
==> app:     
==> app: -------------------
==> app:     
==> app: No route to host - connect(2) for "169.254.169.254" port 80
==> app:     
==> app: 
==> app: 
==> app:     
==> app: Cookbook Trace:
==> app:     ---------------
==> app:     /tmp/vagrant-chef/2a047fdc59eefd5dab7394e72d7474f1/cookbooks/aws/libraries/ec2.rb:85:in `query_instance_availability_zone'
==> app:     /tmp/vagrant-chef/2a047fdc59eefd5dab7394e72d7474f1/cookbooks/aws/libraries/ec2.rb:53:in `instance_availability_zone'
==> app:     /tmp/vagrant-chef/2a047fdc59eefd5dab7394e72d7474f1/cookbooks/aws/libraries/ec2.rb:65:in `create_aws_interface'
==> app:     /tmp/vagrant-chef/2a047fdc59eefd5dab7394e72d7474f1/cookbooks/aws/libraries/s3.rb:9:in `s3'
==> app:     /tmp/vagrant-chef/2a047fdc59eefd5dab7394e72d7474f1/cookbooks/aws/providers/s3_file.rb:33:in `do_s3_file'
==> app:     /tmp/vagrant-chef/2a047fdc59eefd5dab7394e72d7474f1/cookbooks/aws/providers/s3_file.rb:9:in `block in class_from_file'
==> app:     
==> app:     Resource Declaration:
==> app:     ---------------------
==> app:     # In /tmp/vagrant-chef/2a047fdc59eefd5dab7394e72d7474f1/cookbooks/fusion_app_livereview/recipes/geom_server.rb
==> app:     
==> app:      47: aws_s3_file "#{webroot}/tmp/#{codezip_filename}" do
==> app:      48:   bucket bucket
==> app:      49:   remote_path "#{s3bucket}/#{s3pathkey}/#{codezip_filename}"
==> app:      50:   aws_access_key_id aki
==> app:      51:   aws_secret_access_key sak
==> app:      52:   owner 'root'
==> app:      53:   group 'root'
==> app:      54:   mode '0644'
==> app:      55: end
==> app:      56: 


Alvaro Miranda Aguilera

unread,
Aug 19, 2015, 6:33:33 PM8/19/15
to vagra...@googlegroups.com
On Thu, Aug 20, 2015 at 7:00 AM, Roger Micone <rmi...@gmail.com> wrote:
> No route to host - connect(2) for "169.254.169.254" port 80

Hello

The vm in Vagrant using this is also in AWS?

No route to host - connect(2) for "169.254.169.254" port 80

Is not connecting to the metadata url service for some reason.

Roger Micone

unread,
Aug 19, 2015, 9:08:26 PM8/19/15
to Vagrant
confirmed this is a bug in the aws cookbook introduced after version 2.5.0

2.8.0 is supposed to fix this, but using 2.5.0 or lower doesn't have this bug
Reply all
Reply to author
Forward
0 new messages