zanami
commented
8 years ago Had to do
vagrant ssh sudo apt-get install libffi-dev sudo apt-get install libssl-dev sudo pip install pyopenssl
which installed cryptography 1.3
Looks like the underlying problem is this:
The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!
PYTHONUNBUFFERED=1 ANSIBLE_FORCE_COLOR=true ansible-playbook /tmp/mount.yml -i /tmp/inventory --connection=local --sudo --extra-vars "host_os=universal.x86_64-darwin12.0 host_gid=20 host_uid=501 "
Stdout from the command:
Stderr from the command:
Traceback (most recent call last):
File "/usr/local/bin/ansible-playbook", line 4, in
kienanstewart
RealLukeMartin
el capitan virtualbox 5 drush 8 vanilla valkyrie I don't even understand what it's trying to do and where (inside the VM or not).
bash-3.2$ drush vnew valkyrie [notice] Valkyrie project initialized at: valkyrie 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: Setting the name of the VM: valkyrie_valkyrie_1464064637272_76732 ==> valkyrie: Clearing any previously set forwarded ports... ==> 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) => 2222 (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:2222 valkyrie: SSH username: vagrant valkyrie: SSH auth method: private key valkyrie: Warning: Remote connection disconnect. Retrying... valkyrie: Warning: Remote connection disconnect. Retrying... 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: Checking NFS user/group mapping. ==> valkyrie: Fixing NFS user/group mapping. valkyrie: Setting up SSH access for the 'ubuntu' user. valkyrie: Refreshing SSH connection, to login as 'ubuntu'. valkyrie: Installing Ansible from sources. ==> valkyrie: Installing Ansible build dependencies. ==> valkyrie: Using default stable branch: stable-1.9. ==> valkyrie: Cloning Ansible. ==> valkyrie: Running setups tasks for Ansible. The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!
curl -s https://raw.githubusercontent.com/GetValkyrie/ansible-bootstrap/master/install-ansible.sh | /bin/sh
Stdout from the command:
Installing Ansible build dependencies. Using default stable branch: stable-1.9. Cloning Ansible. Running setups tasks for Ansible.
Stderr from the command:
[error] The external command could not be executed due to an application error. [error] The command could not be executed successfully (returned: ssh: Could not resolve hostname valkyrie.val: nodename nor servname provided, or not known , code: 255)