yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

** Attachment added: "wily-sources.list: sources.list produced from ubuntu-15.10-server-amd64.iso"
   https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1177432/+attachment/4512320/+files/wily-sources.list

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

** Description changed:

  [SRU Justification]
  Ubuntu Cloud Images are inconsistent with desktop and bare-metal server installations since backports are not enabled. This is effected via cloud-init that uses a template to select an in-cloud archive.
  
  [FIX] Include the Ubuntu backports in the template.
  
- [REGRESION] The potential for regression is low. However some users will
- likely experience slower fetch times on apt-get updates especially on
- slower or high latency networks.
+ [REGRESION] The potential for regression is low. However all users will
+ experience slower fetch times on apt-get updates especially on slower or
+ high latency networks.
  
  [TEST]
  1. Build image from -proposed
  2. Boot up image
  3. Confirm that "sudo apt-get update" pulls in backports.
  
  Backports are currently not enabled in the cloud-init template. This is
  needed in order to get the backport kernels on cloud images.
  
  Related bugs:
   * bug 997371:  Create command to add "multiverse" and "-backports" to apt sources

** Description changed:

  [SRU Justification]
  Ubuntu Cloud Images are inconsistent with desktop and bare-metal server installations since backports are not enabled. This is effected via cloud-init that uses a template to select an in-cloud archive.
  
  [FIX] Include the Ubuntu backports in the template.
  
- [REGRESION] The potential for regression is low. However all users will
+ [REGRESION] The potential for regression is low. However, all users will
  experience slower fetch times on apt-get updates especially on slower or
  high latency networks.
  
  [TEST]
  1. Build image from -proposed
  2. Boot up image
  3. Confirm that "sudo apt-get update" pulls in backports.
  
  Backports are currently not enabled in the cloud-init template. This is
  needed in order to get the backport kernels on cloud images.
  
  Related bugs:
   * bug 997371:  Create command to add "multiverse" and "-backports" to apt sources

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1177432

Title:
  [SRU] Enable backports in cloud-init archive template

Status in cloud-init:
  New
Status in cloud-init package in Ubuntu:
  In Progress
Status in cloud-init source package in Precise:
  New
Status in cloud-init source package in Trusty:
  New
Status in cloud-init source package in Vivid:
  New
Status in cloud-init source package in Wily:
  New
Status in cloud-init source package in Xenial:
  In Progress

Bug description:
  [SRU Justification]
  Ubuntu Cloud Images are inconsistent with desktop and bare-metal server installations since backports are not enabled. This is effected via cloud-init that uses a template to select an in-cloud archive.

  [FIX] Include the Ubuntu backports in the template.

  [REGRESION] The potential for regression is low. However, all users
  will experience slower fetch times on apt-get updates especially on
  slower or high latency networks.

  [TEST]
  1. Build image from -proposed
  2. Boot up image
  3. Confirm that "sudo apt-get update" pulls in backports.

  Backports are currently not enabled in the cloud-init template. This
  is needed in order to get the backport kernels on cloud images.

  Related bugs:
   * bug 997371:  Create command to add "multiverse" and "-backports" to apt sources

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