FailedConsole Output

Started by user Herman van Rink
Building in workspace /var/lib/jenkins/jobs/D_aegir3-debian-test-unstable-xenial/workspace
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url http://git.drupal.org/project/puppet-aegir.git # timeout=10
Fetching upstream changes from http://git.drupal.org/project/puppet-aegir.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress http://git.drupal.org/project/puppet-aegir.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/1.0.x^{commit} # timeout=10
Checking out Revision 286eab2f1c1c419f47107f897f2ac29d376b4db2 (origin/1.0.x)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 286eab2f1c1c419f47107f897f2ac29d376b4db2
 > git rev-list e79cf23539c635b8df01d8587a4546a90adfe0ff # timeout=10
 > git tag -a -f -m Jenkins Build #20 jenkins-D_aegir3-debian-test-unstable-xenial-20 # timeout=10
[workspace] $ /bin/sh -xe /tmp/hudson6156707875761273695.sh
+ ./tests/functional_tests/aegir3-deb-unstable-no-puppet-xenial/setup.sh
==> default: VM not created. Moving on...
[workspace] $ /bin/sh -xe /tmp/hudson6983892348042909152.sh
+ ./tests/functional_tests/aegir3-deb-unstable-no-puppet-xenial/run-tests.sh
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/xenial64'...

Progress: 90%
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/xenial64' is up to date...
==> default: Setting the name of the VM: ubuntu-xenial-16.04-cloudimg
==> default: Fixed port collision for 22 => 2222. Now on port 2203.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2203 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2203
    default: SSH username: ubuntu
    default: SSH auth method: password
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
==> default: Inserting Vagrant public key within guest...
==> default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: 
    default: Guest Additions Version: 5.0.18_Ubuntu r106667
    default: VirtualBox Version: 4.3
==> default: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

hostname -f

Stdout from the command:



Stderr from the command:

sudo: unable to resolve host ubuntu-xenial
mesg: ttyname failed: Inappropriate ioctl for device
hostname: Name or service not known
'vagrant up' failed. Leaving vm in place for forensic analysis.
Build step 'Execute shell' marked build as failure
Finished: FAILURE