confirmed this is a bug in the aws cookbook introduced after version 2.5.0 https://github.com/opscode-cookbooks/aws/issues/111
2.8.0 is supposed to fix this, but using 2.5.0 or lower doesn't have this bug On Wednesday, August 19, 2015 at 3:33:33 PM UTC-7, Alvaro Miranda Aguilera wrote: > > On Thu, Aug 20, 2015 at 7:00 AM, Roger Micone <[email protected] > <javascript:>> 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. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/4d1f5e37-6105-46cc-bd91-de7f15056ee2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
