[Bug 1605795] [NEW] [SRU] livecd-rootfs ubuntu-cpc vagrant image builder

Fri Jul 22 22:50:43 UTC 2016

Public bug reported:

[Impact]

* The official ubuntu vagrant box for xenial has the following problems:
- synced folders don't work (LP: #1565985)
- the default synced folder is disabled
- only one instance of the box can be run on a host
- localhost name resolution fails (LP: #1561250)

* These issues are all fixed in yakkety by my patch [MR].  We would like
to backport the changes to xenial so that the vagrant boxes for the LTS
release will work correctly.

* The way this fix works is by slightly changing how the vagrant box is
built.  Instead of using the base VMDK image and making a box from that,
we use the ext4 image, install the virtualbox-guest-utils package, then
create our own vmdk for the vagrant box.  The other changes were made to
config files included as vagrant box metadata alongside the vmdk image.

[Test Case]

* Test instructions are explained in comments [MR.1] and [MR.2] in the
original merge request [MR]

* The change was tested and verified on xenial by myself (the original
patch author).

* The change was also tested on yakkety by Dan Watkins using the actual
ubuntu-cpc image building platform and verified by users who downloaded
the box Dan built. (See LP: #1565985 for their verifications.)

[Regression Potential]

* I believe there is little chance of regression because this patch...
- Only affects livecd-rootfs which is a package that is used to build ubuntu distribution disk images, and not needed for running an ubuntu installation
- Only changes one image builder script within livecd-rootfs, ubuntu-cpc/hooks/042-vagrant.binary, which no other builders depend on

* The only possible regression I'm aware of is that the build could fail
if there is not enough free space.  This patch causes the build to use
about 2 GB more space than previously because an extra disk image is
created during the build process (then cleaned up after).

[Other info]

* This patch was developed in collaboration with Dan Watkins (with
review & feedback also by Steve Langasek and Adam Conrad), and I'm
grateful for their help.

* Dan advised me in [IRC] to create this SRU and said that someone will
need to target LP: #1565985.

[Links]

[MR] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305
[MR.1] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/768010
[MR.2] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/770577
[IRC] https://irclogs.ubuntu.com/2016/07/22/%23ubuntu-devel.html#t15:24

** Affects: cloud-images
     Importance: Undecided
         Status: New

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: cloud-images
   Importance: Undecided
       Status: New

** No longer affects: cloud-archive

** Description changed:

  [Impact]

  * The official ubuntu vagrant box for xenial has the following problems:
  - synced folders don't work (LP: #1565985)
  - the default synced folder is disabled
  - only one instance of the box can be run on a host
  - localhost name resolution fails (LP: #1561250)

  * These issues are all fixed in yakkety by my patch [MR].  We would like
  to backport the changes to xenial so that the vagrant boxes for the LTS
  release will work correctly.

  * The way this fix works is by slightly changing how the vagrant box is
  built.  Instead of using the base VMDK image and making a box from that,
  we use the ext4 image, install the virtualbox-guest-utils package, then
  create our own vmdk for the vagrant box.  The other changes were made to
  config files included as vagrant box metadata alongside the vmdk image.

  [Test Case]

  * Test instructions are explained in comments [MR.1] and [MR.2] in the
  original merge request [MR]

  * The change was tested and verified on xenial by myself (the original
  patch author).

  * The change was also tested on yakkety by Dan Watkins using the actual
  ubuntu-cpc image building platform and verified by users who downloaded
- the box Dan built. (See bug report for their verifications.)
+ the box Dan built. (See #1565985 for their verifications.)

  [Regression Potential]

  * I believe there is little chance of regression because this patch...
  - Only affects livecd-rootfs which is a package that is used to build ubuntu distribution disk images, and not needed for running an ubuntu installation
  - Only changes one image builder script within livecd-rootfs, ubuntu-cpc/hooks/042-vagrant.binary, which no other builders depend on

  * The only possible regression I'm aware of is that the build could fail
  if there is not enough free space.  This patch causes the build to use
  about 2 GB more space than previously because an extra disk image is
  created during the build process (then cleaned up after).

  [Other info]

  * This patch was developed in collaboration with Dan Watkins (with
  review & feedback also by Steve Langasek and Adam Conrad), and I'm
  grateful for their help.

  * Dan advised me in [IRC] to create this SRU and said that someone will
  need to target LP: #1565985.

  [Links]

  [MR] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305
  [MR.1] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/768010
  [MR.2] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/770577
  [IRC] https://irclogs.ubuntu.com/2016/07/22/%23ubuntu-devel.html#t15:24

** Description changed:

  [Impact]

  * The official ubuntu vagrant box for xenial has the following problems:
  - synced folders don't work (LP: #1565985)
  - the default synced folder is disabled
  - only one instance of the box can be run on a host
  - localhost name resolution fails (LP: #1561250)

  * These issues are all fixed in yakkety by my patch [MR].  We would like
  to backport the changes to xenial so that the vagrant boxes for the LTS
  release will work correctly.

  * The way this fix works is by slightly changing how the vagrant box is
  built.  Instead of using the base VMDK image and making a box from that,
  we use the ext4 image, install the virtualbox-guest-utils package, then
  create our own vmdk for the vagrant box.  The other changes were made to
  config files included as vagrant box metadata alongside the vmdk image.

  [Test Case]

  * Test instructions are explained in comments [MR.1] and [MR.2] in the
  original merge request [MR]

  * The change was tested and verified on xenial by myself (the original
  patch author).

  * The change was also tested on yakkety by Dan Watkins using the actual
  ubuntu-cpc image building platform and verified by users who downloaded
- the box Dan built. (See #1565985 for their verifications.)
+ the box Dan built. (See LP: #1565985 for their verifications.)

  [Regression Potential]

  * I believe there is little chance of regression because this patch...
  - Only affects livecd-rootfs which is a package that is used to build ubuntu distribution disk images, and not needed for running an ubuntu installation
  - Only changes one image builder script within livecd-rootfs, ubuntu-cpc/hooks/042-vagrant.binary, which no other builders depend on

  * The only possible regression I'm aware of is that the build could fail
  if there is not enough free space.  This patch causes the build to use
  about 2 GB more space than previously because an extra disk image is
  created during the build process (then cleaned up after).

  [Other info]

  * This patch was developed in collaboration with Dan Watkins (with
  review & feedback also by Steve Langasek and Adam Conrad), and I'm
  grateful for their help.

  * Dan advised me in [IRC] to create this SRU and said that someone will
  need to target LP: #1565985.

  [Links]

  [MR] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305
  [MR.1] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/768010
  [MR.2] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/770577
  [IRC] https://irclogs.ubuntu.com/2016/07/22/%23ubuntu-devel.html#t15:24

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1605795

Title:
  [SRU] livecd-rootfs ubuntu-cpc vagrant image builder

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  New

Bug description:
  [Impact]

  * The official ubuntu vagrant box for xenial has the following problems:
  - synced folders don't work (LP: #1565985)
  - the default synced folder is disabled
  - only one instance of the box can be run on a host
  - localhost name resolution fails (LP: #1561250)

  * These issues are all fixed in yakkety by my patch [MR].  We would
  like to backport the changes to xenial so that the vagrant boxes for
  the LTS release will work correctly.

  * The way this fix works is by slightly changing how the vagrant box
  is built.  Instead of using the base VMDK image and making a box from
  that, we use the ext4 image, install the virtualbox-guest-utils
  package, then create our own vmdk for the vagrant box.  The other
  changes were made to config files included as vagrant box metadata
  alongside the vmdk image.

  [Test Case]

  * Test instructions are explained in comments [MR.1] and [MR.2] in the
  original merge request [MR]

  * The change was tested and verified on xenial by myself (the original
  patch author).

  * The change was also tested on yakkety by Dan Watkins using the
  actual ubuntu-cpc image building platform and verified by users who
  downloaded the box Dan built. (See LP: #1565985 for their
  verifications.)

  [Regression Potential]

  * I believe there is little chance of regression because this patch...
  - Only affects livecd-rootfs which is a package that is used to build ubuntu distribution disk images, and not needed for running an ubuntu installation
  - Only changes one image builder script within livecd-rootfs, ubuntu-cpc/hooks/042-vagrant.binary, which no other builders depend on

  * The only possible regression I'm aware of is that the build could
  fail if there is not enough free space.  This patch causes the build
  to use about 2 GB more space than previously because an extra disk
  image is created during the build process (then cleaned up after).

  [Other info]

  * This patch was developed in collaboration with Dan Watkins (with
  review & feedback also by Steve Langasek and Adam Conrad), and I'm
  grateful for their help.

  * Dan advised me in [IRC] to create this SRU and said that someone
  will need to target LP: #1565985.

  [Links]

  [MR] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305
  [MR.1] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/768010
  [MR.2] https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305/comments/770577
  [IRC] https://irclogs.ubuntu.com/2016/07/22/%23ubuntu-devel.html#t15:24

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1605795/+subscriptions