vagrant errors.

gistfile1.txt

[centos-65-x64] Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'aborted' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

----

[centos-65-x64] Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

hostname --fqdn > /etc/mailname

Stdout from the command:

Stderr from the command:

sudo: unable to resolve host ubuntu-server-1310-x64
stdin: is not a tty
hostname: Name or service not known

----

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["sharedfolder", "add", "2d0a3a0c-6136-4505-a9e1-734465dbd1a7", "--name", "/vagrant", "--hostpath", "/home/jenkins/workspace/Puppet_Elasticsearch_Acceptance/RS_SET/debian-70rc1-x64/VM_PUPPET_VERSION/2.7.0/label/metal/.vagrant/beaker_vagrant_files/debian-70rc1-x64.yml"]

Stderr: VBoxManage: error: The machine 'debian-70rc1-x64yml_debian-70rc1-x64_1392662084544_1039' is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LockMachine(a->session, LockType_Write)" at line 1002 of file VBoxManage

----

Progress: 90%There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/jenkins/.vagrant.d/boxes/debian-70rc1-x64-vbox4210-nocm/virtualbox/box.ovf", "--vsys", "0", "--vmname", "debian-70rc1-x64-vbox4210-nocm_1392662144414_75582", "--vsys", "0", "--unit", "9", "--disk", "/home/jenkins/VirtualBox VMs/debian-70rc1-x64-vbox4210-nocm_1392662144414_75582/box-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/jenkins/.vagrant.d/boxes/debian-70rc1-x64-vbox4210-nocm/virtualbox/box.ovf...
OK.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress object failure: NS_ERROR_ABORT

----

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "eca6a72f-1d96-43f9-bc86-60e0d7de14ad", "--nic2", "none", "--nic3", "none", "--nic4", "none", "--nic5", "none", "--nic6", "none", "--nic7", "none", "--nic8", "none"]

Stderr: VBoxManage: error: The machine 'debian-70rc1-x64yml_debian-70rc1-x64_1392662206438_53936' is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LockMachine(a->session, LockType_Write)" at line 462 of file VBoxManageModifyVM.cpp

----

Bringing machine 'debian-73-x64' up with 'virtualbox' provider...
[debian-73-x64] Importing base box 'debian-73-x64-vbox436-nocm'...

Progress: 10%
Progress: 20%
Progress: 30%
Progress: 40%There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/jenkins/.vagrant.d/boxes/debian-73-x64-vbox436-nocm/virtualbox/box.ovf", "--vsys", "0", "--vmname", "debian73_1392662020331_39658", "--vsys", "0", "--unit", "7", "--disk", "/home/jenkins/VirtualBox VMs/debian73_1392662020331_39658/debian73-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/jenkins/.vagrant.d/boxes/debian-73-x64-vbox436-nocm/virtualbox/box.ovf...
OK.
0%...10%...20%...30%...40%...
Progress object failure: NS_ERROR_ABORT

----

[debian-73-x64] Configuring and enabling network interfaces...
Guest-specific operations were attempted on a machine that is not
ready for guest communication. This should not happen and a bug
should be reported.

----

[debian-73-x64] Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifup eth1

Stdout from the command:

Stderr from the command:

stdin: is not a tty
bash: line 2:  3295 Terminated              /sbin/ifup eth1

----

[ubuntu-server-12042-x64] Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

rm /tmp/vagrant-ifcfg-eth1

Stdout from the command:

Stderr from the command:

rm: cannot remove `/tmp/vagrant-ifcfg-eth1': No such file or directory

----