group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1580596@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package livecd-rootfs - 2.408.65

---------------
livecd-rootfs (2.408.65) xenial; urgency=medium

  [ Joshua Powers ]
  * amd64: revert install grub changes on Xenial (LP: #1901906)

livecd-rootfs (2.408.64) xenial; urgency=medium

  [ Joshua Powers ]
  * amd64: always install grub-efi-amd64-signed (LP: #1901906)

livecd-rootfs (2.408.63) xenial; urgency=medium

  [ John Chittum ]
  * Backport Ensure toolsVersion set in vmdk header (LP: #1893898)

livecd-rootfs (2.408.62) xenial; urgency=medium

  [ Dimitri John Ledkov & Joshua Powers ]
  * amd64: always install grub-pc with shim-signed (LP: #1901906), and
    ensure to autoremove packages

  [ Patrick Viafore ]
  * Increase Vagrant disk size from 10G to 40G (LP: #1580596)

  [ Cody Shepherd ]
  * buildd: ext4: change tar transform target to match changes in bionic+
  * buildd: Skip jasper for buildd subproject
  * buildd: Create manifests for buildd tarballs

livecd-rootfs (2.408.61) xenial; urgency=medium

  * SRU: Enable bootable-buildd hooks for Xenial (LP: #1863024)

 -- Robert C Jennings <robert.jennings@xxxxxxxxxxxxx>  Tue, 15 Dec 2020
11:11:14 -0600

** Changed in: livecd-rootfs (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1580596

Title:
  Xenial & bionic vagrant box disk size is too small

Status in cloud-images:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Users could not use vagrant boxes as a full computer (or anything requiring more than 10G of memory). This was a regression from our behavior in 14.04

  [Test Case]

  vagrant init ubuntu/bionic64 (replace with ubuntu/eoan64 or ubuntu/xenial64 as needed)
  vagrant up
  vagrant ssh default
  Run `df -H` inside the vagrant box
  Observe Disk size of drive mounted at / (before the fix it will list ~10G, after the fix it will list ~40G)

  [Regression Potential]

  Making the disk size bigger for vagrant boxes does not increase the
  size of the box when running (not until that extra size is used).
  Therefore, the regression potential is low, as users with under 40G of
  disk space are still able to launch the new Vagrant images without
  running out of space.

  The 40G was also present in 14.04, which should improve confidence
  that our users can use 40G Vagrant images. This has also released with
  20.04.

  [Original Description]
  The ubuntu/xenial64 box has only 10GB of disk whereas it was 40GB with the trusty box.

  This makes the box not really usable as a desktop computer.

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