yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1411582@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/1411582

Title:
  [SRU] Azure data source should auto-detect ephemeral disk location

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

Bug description:
  [Impact]
  The Azure ephemeral disk will not necessarily remain at the same /dev/sd* location between reboots.  This means the drive may not be persistently mounted between reboots. 

  [Test Case]
  1) Boot an Azure instance with a cloud-init including this fix.
  2) Ensure that the ephemeral disk is mounted at /mnt and formatted as ext4
  3) Ensure that /etc/fstab refers to a /dev/disk/... symlink, rather than a /dev/sd* device.

  [Regression Potential]
  We now use a udev rule to discover the location of the disk; we have been assured by Microsoft that this rule will always work, so regression potential is minimal.

  [Original Report]
  Currently we assume it will be /dev/sdb, but this may change. There is an example of how to handle this in the Azure Linux agent.

  To quote stevez in a comment on bug 1410835:

  Device names are not persistent in Linux and could change, so it is
  not guaranteed that the ephemeral disk will be called /dev/sdb.
  Ideally this should be auto-detected in cloud-init at runtime (for
  example, see DeviceForIdePort() in the Azure Linux agent).

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