group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1513529@xxxxxxxxxxxxxxxxxx>]

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

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

  [ Daniel Watkins ]
  * Don't overwrite the default sources.list in cloud images.
  * Replace sources.list generated using COMPONENTS with the sources.list from
    an Ubuntu Server installation (i.e. with all components enabled, and all
    deb-src lines commented).  LP: #1513529.

  [ Chris Glass ]
  * Fix the manifest generation in OVA files so that ovf files don't have
    double extensions.  (LP: #1627931)
  * Fix the OVF's metadata to include Ubuntu specific identifiers and
    descriptions instead of the generic Linux ones.  (LP: #1656293)

  [ Daniel Watkins ]
  * Add replace_grub_root_with_label function thereby consolidating multiple
    uses of the same calls to sed.

  [ Robert C Jennings ]
  * ubuntu-cpc: Remove redundant copy of grub files. (LP: #1637290)

 -- Robert C Jennings <robert.jennings@xxxxxxxxxxxxx>  Thu, 23 Mar 2017
14:40:59 -0400

** 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/1513529

Title:
  cloud images should be built with the same /etc/apt/sources.list as
  server images

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

Bug description:
  [Impact]

  In systems created from cloud images where cloud-init does not run (or
  has not yet run), /etc/apt/sources.list does not have the same
  contents as it has in a server install.  This inconsistency can cause
  image modification/bootstrap to fail.

  [Test Case]

  Examine the cloud image built from livecd-rootfs, and confirm that the
  sources.list matches that in a server ISO install.

  [Regression Potential]

  Limited; the majority of cloud image usage does invoke cloud-init,
  which already writes out a source.list that matches the server ISO.
  This change aligns non-cloud-init usage to the existing norm.

  [Original Report]

  When we were poking around under bug 1177432 we found that
  /etc/apt/sources.list that is built into the image does not match that
  of an installed system.  This /etc/apt/sources.list is used if cloud-
  init did not re-write the file (such as woudl be used if you mounted
  the image directly and ran apt-get update).

  Example showing the problem:
  $ qemu-img create -f qcow2 -b wily/release-20151029/ubuntu-15.10-server-cloudimg-amd64-disk1.img /tmp/disk.img
  $ sudo mount-image-callback /tmp/disk.img --read-only chroot _MOUNTPOINT_ cat /etc/apt/sources.list
  deb http://archive.ubuntu.com/ubuntu/ wily main restricted universe multiverse
  deb http://archive.ubuntu.com/ubuntu/ wily-updates main restricted universe multiverse
  deb http://security.ubuntu.com/ubuntu/ wily-security main restricted universe multiverse

  What we'd like to see here is exactly what we just added to cloud-init.
  For reference, as attached to bug 1177432, see trusty [1] and wily [2] examples.

  For reference, MAAS installed systems end up getting the built-in
  /etc/apt/sources.list with the ubuntu mirrors updated.  So this change
  after making it all the way through will result in maas images having
  the same list as ISO installed systems also.

  --
  [1] https://launchpadlibrarian.net/224142290/trusty-sources.list
  [2] https://launchpadlibrarian.net/224142308/wily-sources.list

  Related bugs:
   * bug 1177432  [SRU] Enable backports in cloud-init archive template

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