group.of.nepali.translators team mailing list archive

[Dan Watkins <daniel.watkins@xxxxxxxxxxxxx>]

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

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

** Changed in: cloud-init
       Status: New => In Progress

** Changed in: cloud-init
     Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu)
     Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu Trusty)
     Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** No longer affects: cloud-init (Ubuntu Wily)

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Precise:
  New
Status in cloud-init source package in Trusty:
  Confirmed
Status in cloud-init source package in Xenial:
  New
Status in cloud-init source package in Yakkety:
  New

Bug description:
  During provisioning cloud-init adds an entry for the ephemeral disk in
  /etc/fstab. After provisioning this entry is correct and points to
  "/dev/disk/azure/resource-part1". This symlink is created dynamically
  by 66-azure-storage.rules.

  For some reason after the first reboot cloud-init overwrites the fstab
  entry and changes the "/dev/disk/azure/resource-part1" to the device
  name that it points to, i.e. /dev/sdb1.  However, this is incorrect
  since /dev/sd* device names are not persistent.

  
  Repro:

  1) Provision an Ubuntu VM on Azure (I tested with 14.04.4)
  2) The fstab entry for the ephemeral disk (/mnt) correctly points to "/dev/disk/azure/resource-part1".
  3) Reboot the VM (sudo reboot)
  4) The fstab entry now incorrectly points to /dev/sdb1 instead of the symlink.

  Impact:
  There is a chance that the customer's ephemeral disk will not be mounted properly if the device names change after a reboot.

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