Ubuntu 16.04 LTS "Xenial Xerus" test [#2726425]

Comment #1

16 May 2016 at 11:51

helmo created an issue. See original summary.

Log in or register to post comments

Comment #2

helmo commented 16 May 2016 at 12:20

Using the ubuntu/xenial64 box:

==> 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

Using geerlingguy/ubuntu1604:

==> default: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

service hostname start

Stdout from the command:



Stderr from the command:

sudo: unable to resolve host vagrant
mesg: ttyname failed: Inappropriate ioctl for device
Failed to start hostname.service: Unit hostname.service is masked.

Log in or register to post comments

Comment #3

niccolox commented 14 July 2016 at 19:54

I am using a Ansible role forked from Valkyrie that installs Aegir 3.6 on Xenial in Vagrant and installs a few platforms (a role from Praxis Labs) https://github.com/niccolox/ansible-role-aegir

platforms and sites seem to install OK

still getting errors with Provision cache clear and registry rebuild

also
sudo service hosting-queued restart
Failed to restart hosting-queued.service: Unit hosting-queued.service not found

overall it seems to work better than before