First time 'vagrant up' doesn't seem to provision?

philipnorton42 commented 10 years ago

I'm just starting out with Vlad so this I could be doing something silly, but my expectations from the Usage section of the documentation is that after creating a settings.yml and issuing the command 'vagrant up', a new box will be created and provisioned with the specified software.

However when I do this, a new box is created. I can vagrant ssh to it, but none of the software is installed. If i run vagrant provision at this point, the software is installed correctly.

Unless I'm missing something, either the documentation is incorrect (need to add that you must run vagrant provision after first vagrant up) or the automatic provision should be happening, but isn't.

Bitbucket: https://bitbucket.org/philipnorton42/vlad/issue/46
Originally Reported By: Nic Rodgers
Originally Created At: 2014-05-14T15:05:40.505

philipnorton42 commented 10 years ago

Awesome :)

Original Comment By: Philip Norton

philipnorton42 commented 10 years ago

I've uninstalled the offending plugin and that has indeed fixed it. Thanks!

Original Comment By: Nic Rodgers

philipnorton42 commented 10 years ago

It looks like Vagrant is falling over before it gets to the ansible step, hence no provisioning running.

Are you able to uninstall the guest additions update plugin at all? I have used it successfully in the past but it looks like it is breaking things?

You could even try updating that plugin and see if that solves things.

Original Comment By: Philip Norton

philipnorton42 commented 10 years ago

Hi Phil.

I was using vagrant 1.5.2, but I've just upgraded to 1.6.2 and the latest VirtualBox and Ansible and tried again.

This time I've simply cloned Vlad from github, renamed example.settings.yml to settings.yml and run vagrant up. Here's the output incase that's any help:

#!txt

nics-air:vlad nic$ vagrant up
Bringing machine 'vlad' up with 'virtualbox' provider...
==> vlad: Importing base box 'vlad'...
==> vlad: Matching MAC address for NAT networking...
==> vlad: Setting the name of the VM: vlad_vlad_1400075733582_22277
==> vlad: Clearing any previously set network interfaces...
==> vlad: Preparing network interfaces based on configuration...
    vlad: Adapter 1: nat
    vlad: Adapter 2: hostonly
==> vlad: Forwarding ports...
    vlad: 22 => 2222 (adapter 1)
==> vlad: Running 'pre-boot' VM customizations...
==> vlad: Booting VM...
==> vlad: Waiting for machine to boot. This may take a few minutes...
    vlad: SSH address: 127.0.0.1:2222
    vlad: SSH username: vagrant
    vlad: SSH auth method: private key
    vlad: Warning: Connection timeout. Retrying...
==> vlad: Machine booted and ready!
GuestAdditions versions on your host (4.3.10) and guest (4.2.0) do not match.
stdin: is not a tty
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
  fakeroot linux-headers-3.2.0-23 make patch
Suggested packages:
  make-doc diffutils-doc
The following NEW packages will be installed:
  dkms fakeroot linux-headers-3.2.0-23 linux-headers-3.2.0-23-generic make
  patch
0 upgraded, 6 newly installed, 0 to remove and 66 not upgraded.
Need to get 12.7 MB of archives.
After this operation, 68.5 MB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ precise/main make amd64 3.81-8.1ubuntu1 [118 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ precise/main patch amd64 2.6.1-3 [80.2 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ precise/main dkms all 2.2.0.3-1ubuntu3 [73.1 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ precise/main fakeroot amd64 1.18.2-1 [87.2 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu/ precise/main linux-headers-3.2.0-23 all 3.2.0-23.36 [11.4 MB]
Get:6 http://us.archive.ubuntu.com/ubuntu/ precise/main linux-headers-3.2.0-23-generic amd64 3.2.0-23.36 [947 kB]
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Fetched 12.7 MB in 40s (313 kB/s)
Selecting previously unselected package make.
(Reading database ... 51095 files and directories currently installed.)
Unpacking make (from .../make_3.81-8.1ubuntu1_amd64.deb) ...
Selecting previously unselected package patch.
Unpacking patch (from .../patch_2.6.1-3_amd64.deb) ...
Selecting previously unselected package dkms.
Unpacking dkms (from .../dkms_2.2.0.3-1ubuntu3_all.deb) ...
Selecting previously unselected package fakeroot.
Unpacking fakeroot (from .../fakeroot_1.18.2-1_amd64.deb) ...
Selecting previously unselected package linux-headers-3.2.0-23.
Unpacking linux-headers-3.2.0-23 (from .../linux-headers-3.2.0-23_3.2.0-23.36_all.deb) ...
Selecting previously unselected package linux-headers-3.2.0-23-generic.
Unpacking linux-headers-3.2.0-23-generic (from .../linux-headers-3.2.0-23-generic_3.2.0-23.36_amd64.deb) ...
Processing triggers for man-db ...
Setting up make (3.81-8.1ubuntu1) ...
Setting up patch (2.6.1-3) ...
Setting up dkms (2.2.0.3-1ubuntu3) ...
Setting up fakeroot (1.18.2-1) ...
update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode.
Setting up linux-headers-3.2.0-23 (3.2.0-23.36) ...
Setting up linux-headers-3.2.0-23-generic (3.2.0-23.36) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-23-generic /boot/vmlinuz-3.2.0-23-generic
Copy iso file /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
stdin: is not a tty
mount: warning: /mnt seems to be mounted read-only.
Installing Virtualbox Guest Additions 4.3.10 - guest version is 4.2.0
stdin: is not a tty
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.3.10 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 4.2.0 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules ...done.
Doing non-kernel setup of the Guest Additions ...done.
You should restart your guest to make sure the new modules are actually used

Installing the Window System drivers
Could not find the X.Org or XFree86 Window System, skipping.
An error occurred during installation of VirtualBox Guest Additions 4.3.10. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
stdin: is not a tty
==> vlad: Checking for guest additions in VM...
==> vlad: Setting hostname...
==> vlad: Configuring and enabling network interfaces...
==> vlad: Exporting NFS shared folders...
==> vlad: Preparing to edit /etc/exports. Administrator privileges will be required...
==> vlad: Mounting NFS shared folders...
==> vlad: Mounting shared folders...
    vlad: /vagrant => /Volumes/www/nictest/gitvlad/vlad
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:

mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant /vagrant
nics-air:vlad nic$ vagrant -v
Vagrant 1.6.2

Original Comment By: Nic Rodgers

philipnorton42 commented 10 years ago

The provisioning step should happen automatically after vagrant up, so I'm not sure why it isn't. Are you running the latest versions of Vagrant, VirtualBox, and Ansible?

Original Comment By: Philip Norton

hashbangcode / vlad

First time 'vagrant up' doesn't seem to provision? #46