Error when running vagrant up --provider virtualbox

[pgporada]

OS

Ubuntu 14.04

Vagrant version

Installed Version: 1.7.4
Latest Version: 1.7.4

Here is what happens when I start the vagrants up

==> swarm-1: ----> Installing puppet
==> swarm-1: Successfully installed facter-2.4.4
==> swarm-1: Successfully installed json_pure-1.8.2
==> swarm-1: Successfully installed puppet-3.7.5
==> swarm-1: 3 gems installed
==> swarm-1: Successfully installed facter-2.4.4
==> swarm-1: 1 gem installed
==> swarm-1: Running provisioner: hosts...
==> swarm-1: Running provisioner: puppet...
==> swarm-1: Running Puppet with base.pp...
==> swarm-1: stdin: is not a tty
==> swarm-1: Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
==> swarm-1:    (at /var/lib/gems/2.0.0/gems/puppet-3.7.5/lib/puppet/settings.rb:1139:in `issue_deprecation_warning')
==> swarm-1: Debug: Runtime environment: puppet_version=3.7.5, ruby_version=2.0.0, run_mode=user, default_encoding=UTF-8
==> swarm-1: ldapname is deprecated and will be removed in a future version
==> swarm-1: Debug: Loading external facts from /var/lib/puppet/facts.d
==> swarm-1: Error loading fact /usr/lib/ruby/vendor_ruby/facter/macosx.rb: cannot load such file -- cfpropertylist
==> swarm-1: Facter::Util::EC2.has_euca_mac? is deprecated; see the Facter::EC2 classes instead
==> swarm-1: Facter::Util::EC2.has_openstack_mac? is deprecated; see the Facter::EC2 classes instead
==> swarm-1: Facter::Util::EC2.has_ec2_arp? is deprecated; see the Facter::EC2 classes instead
==> swarm-1: Debug: hiera(): Hiera YAML backend starting
==> swarm-1: Debug: hiera(): Looking up classes in YAML backend
==> swarm-1: Debug: hiera(): Looking for data source swarm-1
==> swarm-1: Debug: hiera(): Looking for data source common
==> swarm-1: Debug: hiera(): Found classes in common
==> swarm-1: Error: Could not find class apt for swarm-1.danlawinc.com on node swarm-1.danlawinc.com
==> swarm-1: Error: Could not find class apt for swarm-1.danlawinc.com on node swarm-1.danlawinc.com
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.

Additionally, I needed to install the a vagrant plugin to prevent the following error

vagrant plugin install vagrant-hosts

11:49 AM:phil@PhilsLaptop (master) ~/vagrantworkshop/puppet-docker-swarm-example$ vagrant up --provider virtualbox                                                  
Bringing machine 'swarm-1' up with 'virtualbox' provider...
Bringing machine 'swarm-2' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The 'hosts' provisioner could not be found.

puppet provisioner:
* The configured module path doesn't exist: /home/phil/vagrantworkshop/puppet-docker-swarm-example/modules
* The configured module path doesn't exist: /home/phil/vagrantworkshop/puppet-docker-swarm-example/vendor/modules

[stwomack]

vagrant plugin install vagrant-hosts