← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1456684] Re: [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones

 

** Summary changed:

- does not know central (eu-central-1) is a direction for ec2 zones
+ [SRU] cloud-init does not know central (eu-central-1) is a direction for ec2 zones

** Also affects: cloud-init (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Vivid)
   Importance: Undecided
       Status: New

-- 
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/1456684

Title:
  [SRU] cloud-init does not know central (eu-central-1) is a direction
  for ec2 zones

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
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

Bug description:
  cloud-init's code that tries to determine if it is in a ec2 region is
  simply unaware of the 'central' direction.

  [Impact]
  Ubuntu instances launched in the eu-central-1 EC2 region will not discover region-local mirrors. The user will see a degraded experience as they have to interact with mirrors that are further away and under heavier load. They will also potentially have to pay for the bandwidth used this way (as will the default mirror admins).

  [Test Case]
  Launch an instance in eu-central-1 and examine the apt sources used.  They should be of the form "eu-central-1.ec2.archive.ubuntu.com" instead of "eu-central-1a.clouds.archive.ubuntu.com".

  [Regression Potential]
  Limited; the changes are limited to the mirror discovery, and if mirror discovery fails, we have default mirrors that we will use.

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


References