Box creation currently erroring

[BrianGilbert]

$ 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 '20150818.0.0'. The latest is version '20150821.0.1'. Run
==> valkyrie: `vagrant box update` to update.
==> valkyrie: Setting the name of the VM: valkyrie_valkyrie_1441019881965_75402
==> valkyrie: Clearing any previously set forwarded ports...
==> valkyrie: Pruning invalid NFS exports. Administrator privileges will be required...
Password:
==> 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 => 2222 (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: Connection timeout. 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.10
    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.
==> valkyrie: /bin/sh: 82: cd: can't cd to /usr/local/lib/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:

/bin/sh: 82: cd: can't cd to /usr/local/lib/ansible/

The external command could not be executed due to an application error.                                                     [error]
Illegal string offset 'site' backend.inc:1030                                                                               [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)
3.99s user 1.86s system 0% cpu 12:17.00s total

[ergonlogic]

Start by downgrading to VirtualBox 4.x. Vagrant itself has multiple bugs when running on 5. We'll track progress on that in #81.

[BrianGilbert]

Unfortunately can't run VB 4.x on El Capitan.

A clean build works, but I lose access to internal hostnames after I vagrant halt and re-up

[MatthewHager]

I'm running everything on the latest version on Yosemite and it is working properly.

[BrianGilbert]

@MatthewHager Yosemite != El Capitan

[MatthewHager]

Meaning I'm running vbox 5 and latest vagrant. But thanks for letting me know Yosemite and El Capitan are different.

[BrianGilbert]

@MatthewHager ah.. I thought you were replying to me :)

[MatthewHager]

I will try again today and make sure, but we should be working on latest Vbox/Vagrant if you have the very latest Valkyrie.

I'll try to remember to report back here.

[ergonlogic]

What does this mean, exactly?

A clean build works, but I lose access to internal hostnames after I vagrant halt and re-up

The original issue appears to show that nothing is being installed in the vbox. AFAICT, that error appears to be an issue with https://github.com/GetValkyrie/ansible-bootstrap.

[BrianGilbert]

@ergonlogic this may be an erroneous issue posting..

is the process to halt and start a valkyrie instance just to use the vagrant commands? or is there extra glue that is managed by Drush?

[RealLukeMartin]

It should be perfectly fine to vagrant halt and vagrant up, in fact its the only way we stop and start our boxes.

Do you have any vagrant plugins present? Sometimes they can mess with things.

[BrianGilbert]

halt and up appear to be working fine with latest version