-
Notifications
You must be signed in to change notification settings - Fork 573
Can't provision aws boxes #331
Comments
I'm facing exactly the same problem with vagrant 1.7.1 + vagrant-aws 0.6.0 Does anyone know any workarounds? On Thu, Dec 18, 2014 at 9:38 PM, Jay Janssen notifications@github.com
|
Downgrading vagrant-aws back to 0.5.0 worked for me in the interim.
Jay Janssen, Managing Consultant, Percona |
Yeah, I know. 2014年12月19日金曜日、Jay Janssennotifications@github.comさんは書きました:
|
I am also having this issue. I specifically use rsync and it still complains. If anyone has suggestions please share! |
Had similiar issue (also hit that bug #327 (comment) but replaced certs and it works) : vagrant-aws (0.6.0) Downgrading to 0.5.0 fixes that error message. |
Vagrant 1.7.1's SyncedFolders won't work with Vagrant AWS plugin. So I made a patch to revive previous custom SyncedFolders and this works [ https://github.com/kmizumar/vagrant-aws branch: modified ] % git diff v0.6.0 HEAD diff --git a/CHANGELOG.md b/CHANGELOG.md index 4600e19..5cd9e92 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,11 @@ -# 0.5.1 +# 0.6.1 (January 6, 2015) +* Quick and Dirty Hack to avoid Vagrant SyncedFolders problem. +# 0.6.0 (December 13, 2014)
+* Support for creating AMIs with the 0.5.0 (June 22, 2014)@@ -12,6 +17,8 @@
+* Simple ELB support (GH #88,
0.4.1 (December 17, 2013)diff --git a/README.md b/README.md index a9a476e..fc853b7 100644 --- a/README.md +++ b/README.md @@ -137,6 +137,7 @@ This provider exposes quite a few provider-specific
+* These can be set like typical provider-specific configuration: @@ -195,7 +196,8 @@ There is minimal support for synced folders. Upon
the remote machine over SSH. -See Vagrant Synced folders: rsync +This is good enough for all built-in Vagrant provisioners (shell, +chef, and puppet) to work! Other Examples@@ -249,7 +251,7 @@ Vagrant.configure("2") do |config| end
|
I also had this problem and worked around it successfully by either disabling the default
Or if you need it, by switching from the default NFS to use rsync using:
It'd be nice for it to work out of the box though! |
Would be nice to see this addressed. For some reason, Vagrant 1.7.2 + vagrant-aws 0.6.0 works fine for me on Mac, but the exact same versions and configuration fails on Linux with this error. I already had |
There is a work around suggested in this blog post: http://blog.damore.it/2015/01/aws-vagrant-no-host-ip-was-given-to.html that worked for me.
|
No host IP was given to the Vagrant core NFS helper. This is an internal error that should be reported as a bug. (see mitchellh/vagrant-aws#331) [ci skip]
Any time I try to provision aws boxes on the latest vagrant-aws + vagrant, I get this error:
I am able to ssh, just not provision.
This was working fine until my vagrant-aws upgrade from 0.5.0
The text was updated successfully, but these errors were encountered: