Configure the xenial vagrant box the same way as the trusty

Bug #1581347 reported by christophe on 2016-05-13
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
cloud-images
Undecided
Unassigned

Bug Description

Currently it's not easy to migrate from the trusty vagrant box to the xenial box because of several differences :
- the vagrant user is not configured (#1569237)
- the virtual box extensions are not installed
- sudo doesn't resolve the hostname (#1561250)
- the disk space is 10GB instead of 40GB (#1580596)

I think that the process that was used to package the trusty box hasn't been used to package the xenial box. It seems the xenial box is a simple packaging of the raw image without any specific configuration for vagrant.

To see what should be done for a vagrant base box : https://www.vagrantup.com/docs/boxes/base.html

description: updated
description: updated
Oliver Chick (oc243) wrote :

The xenial box also doesn't have puppet-common installed, so I have had to insert a (nasty) inline shell to install it from apt-get.

Also, sound support is enabled under Xenial, at Trusty it is disabled.

Both disks are SCSI at Xenial, for Trusty both are SATA.

Why packagers took a very different approach under Xenial?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers