[Bug 1513529] Re: cloud images should be built with the same /etc/apt/sources.list as server images
Dan Watkins
daniel.watkins at canonical.com
Thu Jun 9 13:28:40 UTC 2016
So to fix the specific issue that was blocking juju and MAAS, -backports
has been enabled in precise and trusty images.
yakkety images will have the same sources.list as in the server
installation (albeit via a one-time sync).
As xenial has been released with a difference between the sources.lists
and there isn't a currently compelling reason to modify it under users,
we won't make the change there. If, in the future, there is a specific
reason to revisit this decision, we will be happy to do so then.
** Changed in: cloud-images
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
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
Bug description:
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
More information about the foundations-bugs
mailing list