vagrant-aws provision

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

vagrant-aws provision

Stefan Goethals
I used a 'random' CentOS 6.3 ami image.

Provision fails even though the user designated can perform the required action...

Maybe i'm just not performing the necessary steps but i cannot find any docs on what is needed to create a Vagrant compliant ami.


android18:aws01 zipkid$ vagrant provision
[default] Rsyncing folder: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/ => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'


android18:aws01 zipkid$ ssh -i ~/.ssh/zip_kid.pem [hidden email] mkdir -p /vagrant
android18:aws01 zipkid$ echo $?
0


And with debug output...

android18:aws01 zipkid$ VAGRANT_LOG=info vagrant provision
 INFO global: Vagrant version: 1.1.1
 INFO manager: Registered plugin: box command
 INFO manager: Registered plugin: destroy command
 INFO manager: Registered plugin: halt command
 INFO manager: Registered plugin: init command
 INFO manager: Registered plugin: package command
 INFO manager: Registered plugin: plugin command
 INFO manager: Registered plugin: provision command
 INFO manager: Registered plugin: reload command
 INFO manager: Registered plugin: resume command
 INFO manager: Registered plugin: ssh command
 INFO manager: Registered plugin: ssh-config command
 INFO manager: Registered plugin: status command
 INFO manager: Registered plugin: suspend command
 INFO manager: Registered plugin: up command
 INFO manager: Registered plugin: ssh communiator
 INFO manager: Registered plugin: Arch guest
 INFO manager: Registered plugin: Debian guest
 INFO manager: Registered plugin: Fedora guest
 INFO manager: Registered plugin: FreeBSD guest
 INFO manager: Registered plugin: Gentoo guest
 INFO manager: Registered plugin: Linux guest.
 INFO manager: Registered plugin: OpenBSD guest
 INFO manager: Registered plugin: RedHat guest
 INFO manager: Registered plugin: Solaris guest.
 INFO manager: Registered plugin: SUSE guest
 INFO manager: Registered plugin: Ubuntu guest
 INFO manager: Registered plugin: Arch host
 INFO manager: Registered plugin: BSD host
 INFO manager: Registered plugin: Fedora host
 INFO manager: Registered plugin: FreeBSD host
 INFO manager: Registered plugin: Gentoo host
 INFO manager: Registered plugin: Linux host
 INFO manager: Registered plugin: OpenSUSE host
 INFO manager: Registered plugin: Windows host
 INFO manager: Registered plugin: kernel
 INFO manager: Registered plugin: kernel
 INFO manager: Registered plugin: VirtualBox provider
 INFO manager: Registered plugin: chef
 INFO manager: Registered plugin: puppet
 INFO manager: Registered plugin: shell
 INFO vagrant: `vagrant` invoked: ["provision"]
 INFO environment: Environment initialized (#<Vagrant::Environment:0x000001013b3880>)
 INFO environment:   - cwd: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01
 INFO environment: Home path: /Users/zipkid/.vagrant.d
 INFO environment: Local data path: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/.vagrant
 INFO environment: Loading plugin from JSON: vagrant-aws
 INFO manager: Registered plugin: AWS
 INFO environment: Running hook: environment_load
 INFO environment: Initializing config...
 INFO loader: Set :default = "/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/config/default.rb"
 INFO loader: Set :root = #<Pathname:/Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/Vagrantfile>
 INFO loader: Loading configuration in order: [:default, :home, :root]
 INFO hosts: Host class: VagrantPlugins::HostBSD::Host
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000010142e558>
 INFO cli: CLI: [] "provision" []
 INFO command: Active machine found with name default. Using provider: aws
 INFO environment: Getting machine: default (aws)
 INFO environment: Uncached load of machine.
 INFO loader: Set :vm_default = []
 INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
 INFO box_collection: Searching for box: aws (aws) in /Users/zipkid/.vagrant.d/boxes/aws/aws/metadata.json
 INFO box_collection: Box found: aws (aws)
 INFO environment: Box exists with Vagrantfile. Reloading machine config.
 INFO loader: Set :box_aws_aws = #<Pathname:/Users/zipkid/.vagrant.d/boxes/aws/aws/Vagrantfile>
 INFO loader: Loading configuration in order: [:default, :box_aws_aws, :home, :root, :vm_default]
 INFO machine: Initializing machine: default
 INFO machine:   - Provider: VagrantPlugins::AWS::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x00000101440e60>
 INFO machine:   - Data dir: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/.vagrant/machines/default/aws
 INFO command: With machine: default (AWS (i-524d3118))
 INFO machine: Calling action: provision on provider AWS (i-524d3118)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000101422c08>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x000001010463f0>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::Call:0x00000101046378>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000001011b58f8>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::IsCreated:0x000001011c45b0>
 INFO machine: Calling action: read_state on provider AWS (i-524d3118)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000001012970c8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x0000010159d588>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x0000010159d510>
 INFO connect_aws: Connecting to AWS...
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadState:0x0000010150ddc0>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x000001013ffcf8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::Provision:0x000001013ffc08>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::SyncFolders:0x000001017c5428>
 INFO machine: Calling action: read_ssh_info on provider AWS (i-524d3118)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000010173c358>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x0000010140b800>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x0000010140b5f8>
 INFO connect_aws: Connecting to AWS...
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadSSHInfo:0x000001010a9e28>
 INFO interface: info: Rsyncing folder: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/ => /vagrant
[default] Rsyncing folder: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/ => /vagrant
 INFO machine: Calling action: read_ssh_info on provider AWS (i-524d3118)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100dfd0f8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000100e63358>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x00000100e63330>
 INFO connect_aws: Connecting to AWS...
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadSSHInfo:0x00000100e77150>
 INFO ssh: Attempting SSH. Retries: 100. Timeout: 30
 INFO ssh: Attempting to connect to SSH: ec2-54-246-41-216.eu-west-1.compute.amazonaws.com:22
 INFO ssh: Execute: mkdir -p '/vagrant' (sudo=true)
ERROR warden: Error occurred: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000101046378>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 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:0x000001017dd4b0>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::VagrantError: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'>
ERROR vagrant: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'
ERROR vagrant: /Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/communicators/ssh/communicator.rb:70:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/communicators/ssh/communicator.rb:80:in `sudo'
/Users/zipkid/.vagrant.d/gems/gems/vagrant-aws-0.1.1/lib/vagrant-aws/action/sync_folders.rb:34:in `block in call'
/Users/zipkid/.vagrant.d/gems/gems/vagrant-aws-0.1.1/lib/vagrant-aws/action/sync_folders.rb:21:in `each'
/Users/zipkid/.vagrant.d/gems/gems/vagrant-aws-0.1.1/lib/vagrant-aws/action/sync_folders.rb:21:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/provision.rb:45:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/runner.rb:61:in `block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/runner.rb:61:in `run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/call.rb:51:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builder.rb:109:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/runner.rb:61:in `block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/runner.rb:61:in `run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/machine.rb:129:in `action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/commands/provision/command.rb:26:in `block in execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/plugin/v2/command.rb:182:in `block in with_target_vms'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/plugin/v2/command.rb:180:in `each'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/plugin/v2/command.rb:180:in `with_target_vms'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/commands/provision/command.rb:25:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/cli.rb:46:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/environment.rb:406:in `cli'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/bin/vagrant:60:in `<top (required)>'
/Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `load'
/Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `<main>'
 INFO interface: error: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant-aws provision

Stefan Goethals
Ok, Never Mind me... i just found i need to disable 'requiretty' in the sudoers file :-)

Sorry,


Stefan.


On Mon, Mar 18, 2013 at 10:30 PM, Stefan Goethals <[hidden email]> wrote:
I used a 'random' CentOS 6.3 ami image.

Provision fails even though the user designated can perform the required action...

Maybe i'm just not performing the necessary steps but i cannot find any docs on what is needed to create a Vagrant compliant ami.


android18:aws01 zipkid$ vagrant provision
[default] Rsyncing folder: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/ => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'


android18:aws01 zipkid$ ssh -i ~/.ssh/zip_kid.pem [hidden email] mkdir -p /vagrant
android18:aws01 zipkid$ echo $?
0


And with debug output...

android18:aws01 zipkid$ VAGRANT_LOG=info vagrant provision
 INFO global: Vagrant version: 1.1.1
 INFO manager: Registered plugin: box command
 INFO manager: Registered plugin: destroy command
 INFO manager: Registered plugin: halt command
 INFO manager: Registered plugin: init command
 INFO manager: Registered plugin: package command
 INFO manager: Registered plugin: plugin command
 INFO manager: Registered plugin: provision command
 INFO manager: Registered plugin: reload command
 INFO manager: Registered plugin: resume command
 INFO manager: Registered plugin: ssh command
 INFO manager: Registered plugin: ssh-config command
 INFO manager: Registered plugin: status command
 INFO manager: Registered plugin: suspend command
 INFO manager: Registered plugin: up command
 INFO manager: Registered plugin: ssh communiator
 INFO manager: Registered plugin: Arch guest
 INFO manager: Registered plugin: Debian guest
 INFO manager: Registered plugin: Fedora guest
 INFO manager: Registered plugin: FreeBSD guest
 INFO manager: Registered plugin: Gentoo guest
 INFO manager: Registered plugin: Linux guest.
 INFO manager: Registered plugin: OpenBSD guest
 INFO manager: Registered plugin: RedHat guest
 INFO manager: Registered plugin: Solaris guest.
 INFO manager: Registered plugin: SUSE guest
 INFO manager: Registered plugin: Ubuntu guest
 INFO manager: Registered plugin: Arch host
 INFO manager: Registered plugin: BSD host
 INFO manager: Registered plugin: Fedora host
 INFO manager: Registered plugin: FreeBSD host
 INFO manager: Registered plugin: Gentoo host
 INFO manager: Registered plugin: Linux host
 INFO manager: Registered plugin: OpenSUSE host
 INFO manager: Registered plugin: Windows host
 INFO manager: Registered plugin: kernel
 INFO manager: Registered plugin: kernel
 INFO manager: Registered plugin: VirtualBox provider
 INFO manager: Registered plugin: chef
 INFO manager: Registered plugin: puppet
 INFO manager: Registered plugin: shell
 INFO vagrant: `vagrant` invoked: ["provision"]
 INFO environment: Environment initialized (#<Vagrant::Environment:0x000001013b3880>)
 INFO environment:   - cwd: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01
 INFO environment: Home path: /Users/zipkid/.vagrant.d
 INFO environment: Local data path: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/.vagrant
 INFO environment: Loading plugin from JSON: vagrant-aws
 INFO manager: Registered plugin: AWS
 INFO environment: Running hook: environment_load
 INFO environment: Initializing config...
 INFO loader: Set :default = "/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/config/default.rb"
 INFO loader: Set :root = #<Pathname:/Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/Vagrantfile>
 INFO loader: Loading configuration in order: [:default, :home, :root]
 INFO hosts: Host class: VagrantPlugins::HostBSD::Host
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000010142e558>
 INFO cli: CLI: [] "provision" []
 INFO command: Active machine found with name default. Using provider: aws
 INFO environment: Getting machine: default (aws)
 INFO environment: Uncached load of machine.
 INFO loader: Set :vm_default = []
 INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
 INFO box_collection: Searching for box: aws (aws) in /Users/zipkid/.vagrant.d/boxes/aws/aws/metadata.json
 INFO box_collection: Box found: aws (aws)
 INFO environment: Box exists with Vagrantfile. Reloading machine config.
 INFO loader: Set :box_aws_aws = #<Pathname:/Users/zipkid/.vagrant.d/boxes/aws/aws/Vagrantfile>
 INFO loader: Loading configuration in order: [:default, :box_aws_aws, :home, :root, :vm_default]
 INFO machine: Initializing machine: default
 INFO machine:   - Provider: VagrantPlugins::AWS::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x00000101440e60>
 INFO machine:   - Data dir: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/.vagrant/machines/default/aws
 INFO command: With machine: default (AWS (i-524d3118))
 INFO machine: Calling action: provision on provider AWS (i-524d3118)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000101422c08>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x000001010463f0>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::Call:0x00000101046378>
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000001011b58f8>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::IsCreated:0x000001011c45b0>
 INFO machine: Calling action: read_state on provider AWS (i-524d3118)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x000001012970c8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x0000010159d588>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x0000010159d510>
 INFO connect_aws: Connecting to AWS...
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadState:0x0000010150ddc0>
 INFO runner: Running action: #<Vagrant::Action::Warden:0x000001013ffcf8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::Provision:0x000001013ffc08>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::SyncFolders:0x000001017c5428>
 INFO machine: Calling action: read_ssh_info on provider AWS (i-524d3118)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000010173c358>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x0000010140b800>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x0000010140b5f8>
 INFO connect_aws: Connecting to AWS...
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadSSHInfo:0x000001010a9e28>
 INFO interface: info: Rsyncing folder: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/ => /vagrant
[default] Rsyncing folder: /Volumes/Source/Eclipse-workspace/Zipkid/vagrant/aws01/ => /vagrant
 INFO machine: Calling action: read_ssh_info on provider AWS (i-524d3118)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x00000100dfd0f8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000100e63358>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x00000100e63330>
 INFO connect_aws: Connecting to AWS...
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadSSHInfo:0x00000100e77150>
 INFO ssh: Attempting SSH. Retries: 100. Timeout: 30
 INFO ssh: Attempting to connect to SSH: ec2-54-246-41-216.eu-west-1.compute.amazonaws.com:22
 INFO ssh: Execute: mkdir -p '/vagrant' (sudo=true)
ERROR warden: Error occurred: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000101046378>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 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:0x000001017dd4b0>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::VagrantError: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'>
ERROR vagrant: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'
ERROR vagrant: /Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/communicators/ssh/communicator.rb:70:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/communicators/ssh/communicator.rb:80:in `sudo'
/Users/zipkid/.vagrant.d/gems/gems/vagrant-aws-0.1.1/lib/vagrant-aws/action/sync_folders.rb:34:in `block in call'
/Users/zipkid/.vagrant.d/gems/gems/vagrant-aws-0.1.1/lib/vagrant-aws/action/sync_folders.rb:21:in `each'
/Users/zipkid/.vagrant.d/gems/gems/vagrant-aws-0.1.1/lib/vagrant-aws/action/sync_folders.rb:21:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/provision.rb:45:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/runner.rb:61:in `block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/runner.rb:61:in `run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/call.rb:51:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builder.rb:109:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/runner.rb:61:in `block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/runner.rb:61:in `run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/machine.rb:129:in `action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/commands/provision/command.rb:26:in `block in execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/plugin/v2/command.rb:182:in `block in with_target_vms'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/plugin/v2/command.rb:180:in `each'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/plugin/v2/command.rb:180:in `with_target_vms'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/commands/provision/command.rb:25:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/cli.rb:46:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/environment.rb:406:in `cli'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.1.1/bin/vagrant:60:in `<top (required)>'
/Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `load'
/Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `<main>'
 INFO interface: error: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mkdir -p '/vagrant'

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.