search

GetValkyrie / valkyrie

Valkyrie is an opinionated local dev stack that makes features/git based Drupal development easy.
http://www.getvalkyrie.com
GNU General Public License v3.0
45 stars 11 forks source link

valkyrie: /tmp/vagrant-shell: line 1: ansible-playbook: command not found #90

Closed proofoftom closed 5 years ago

proofoftom commented 8 years ago

I'm having the same issue as #48 running the following versions:

Virtualbox 5.0.16 Vagrant 1.8.1 Drush 7.4-dev

With these vagrant plugins:

vagrant-auto_network (1.0.2) vagrant-berkshelf (4.1.0) vagrant-cachier (1.2.1) vagrant-dnsmasq (0.1.1) vagrant-gatling-rsync (0.9.0) vagrant-hostsupdater (1.0.2) vagrant-omnibus (1.4.1) vagrant-protobox (0.0.2) vagrant-scp (0.5.7) vagrant-share (1.1.5, system) vagrant-triggers (0.5.3)

Output:

$ drush vnew valkyrie
Valkyrie project initialized at: valkyrie                                                                               [ok]
Bringing machine 'valkyrie' up with 'virtualbox' provider...
==> valkyrie: Importing base box 'ubuntu/trusty64'...
==> valkyrie: Matching MAC address for NAT networking...
==> valkyrie: Checking if box 'ubuntu/trusty64' is up to date...
==> valkyrie: A newer version of the box 'ubuntu/trusty64' is available! You currently
==> valkyrie: have version '20160406.0.0'. The latest is version '20160509.1.0'. Run
==> valkyrie: `vagrant box update` to update.
==> valkyrie: Setting the name of the VM: valkyrie_valkyrie_1463177482447_47759
==> valkyrie: Clearing any previously set forwarded ports...
==> valkyrie: Fixed port collision for 22 => 2222. Now on port 2200.
==> valkyrie: Clearing any previously set network interfaces...
==> valkyrie: Preparing network interfaces based on configuration...
    valkyrie: Adapter 1: nat
    valkyrie: Adapter 2: hostonly
==> valkyrie: Forwarding ports...
    valkyrie: 22 (guest) => 2200 (host) (adapter 1)
==> valkyrie: Running 'pre-boot' VM customizations...
==> valkyrie: Booting VM...
==> valkyrie: Waiting for machine to boot. This may take a few minutes...
    valkyrie: SSH address: 127.0.0.1:2200
    valkyrie: SSH username: vagrant
    valkyrie: SSH auth method: private key
    valkyrie:
    valkyrie: Vagrant insecure key detected. Vagrant will automatically replace
    valkyrie: this with a newly generated keypair for better security.
    valkyrie:
    valkyrie: Inserting generated public key within guest...
    valkyrie: Removing insecure key from the guest if it's present...
    valkyrie: Key inserted! Disconnecting and reconnecting using new SSH key...
==> valkyrie: Machine booted and ready!
==> valkyrie: Checking for guest additions in VM...
    valkyrie: The guest additions on this VM do not match the installed version of
    valkyrie: VirtualBox! In most cases this is fine, but in rare cases it can
    valkyrie: prevent things such as shared folders from working properly. If you see
    valkyrie: shared folder errors, please make sure the guest additions within the
    valkyrie: virtual machine match the version of VirtualBox you have installed on
    valkyrie: your host and reload your VM.
    valkyrie:
    valkyrie: Guest Additions Version: 4.3.36
    valkyrie: VirtualBox Version: 5.0
==> valkyrie: [vagrant-hostsupdater] Checking for host entries
==> valkyrie: [vagrant-hostsupdater] Writing the following entries to (/etc/hosts)
==> valkyrie: [vagrant-hostsupdater]   10.42.0.10  valkyrie.local  # VAGRANT: 39a9fa9d84bad5ab2256c6126bc4a57e (valkyrie) / f9a887fe-443e-4752-95b8-d8bea4ac8eae
==> valkyrie: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> valkyrie: Setting hostname...
==> valkyrie: Configuring and enabling network interfaces...
==> valkyrie: Exporting NFS shared folders...
==> valkyrie: Preparing to edit /etc/exports. Administrator privileges will be required...
==> valkyrie: Mounting NFS shared folders...
==> valkyrie: Mounting shared folders...
    valkyrie: /vagrant => /Users/tommy/vagrant/valkyrie
==> valkyrie: Running provisioner: file...
==> valkyrie: Running provisioner: shell...
    valkyrie: Running: inline script
==> valkyrie: /tmp/vagrant-shell: line 1: ansible-playbook: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
==> valkyrie: The previous process exited with exit code 1.
The external command could not be executed due to an application error.                                                 [error]
Illegal string offset 'site' backend.inc:1032                                                                           [warning]
The command could not be executed successfully (returned: ssh: Could not resolve hostname valkyrie.val: nodename nor    [error]
servname provided, or not known
, code: 255)