yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1470880@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.8

---------------
cloud-init (0.7.5-0ubuntu1.8) trusty; urgency=medium

  * debian/patches/lp-1411582-azure-udev-ephemeral-disks.patch:
      - Use udev rules to discover ephemeral disk locations rather than
        hard-coded device names (LP: #1411582).
  * debian/patches/lp-1470880-fix-gce-az-determination.patch:
      - Correctly parse GCE's availability zones (LP: #1470880).
  * d/patches/lp-1470890-include-regions-in-dynamic-mirror-discovery.patch:
      - Make %(region)s a valid substitution in mirror discovery
        (LP: #1470890).
  * Remove python-serial from Build-Depends; it was mistakenly added last
    upload.

 -- Daniel Watkins <daniel.watkins@xxxxxxxxxxxxx>  Fri, 14 Aug 2015
13:54:02 +0100

** Changed in: cloud-init (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

** Changed in: cloud-init (Ubuntu Vivid)
       Status: Fix Committed => Fix Released

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

Title:
  [SRU] GCE datasource reports availability zones incorrectly

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Precise:
  Fix Released
Status in cloud-init source package in Trusty:
  Fix Released
Status in cloud-init source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  Availability zones and regions on GCE cannot be used for mirror substitution, making in-cloud mirrors impossible.

  [Test Case]
  Run the following Python code on trusty and later:

  from cloudinit.sources.DataSourceGCE import DataSourceGCE
  ds = DataSourceGCE({}, None, None)
  ds.get_data()
  ds.availability_zone

  Or the following code on precise:

  from cloudinit.DataSourceGCE import DataSourceGCE
  ds = DataSourceGCE({})
  ds.get_data()
  ds.get_availability_zone()

  and confirm that the availability zone is returned (rather than a
  relative URL).

  [Regression Potential]
  This is completely broken at the moment, so it can't get any more broken.

  [Original Report]
  After querying the cloud fabric, DataSourceGCE will return something along the lines of "projects/969378662406/zones/europe-west1-d" as its availability_zone.

  This means that other parts of the code that expect a sensible value
  for this (most notably the mirror discovery code), are broken on GCE.

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