This is fixed in commit
9e904bbc3336b96475bfd00fb3bf1262ae4de49f
https://git.launchpad.net/cloud-init/commit/?id=9e904bbc3336b96475bfd00fb3bf1262ae4de49f
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init
Status: In Progress => Fix Committed
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Description changed:
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.
+
+ Related bugs:
+ * bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM
--
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/1603222
Title:
Azure: incorrect entry in fstab for ephemeral disk
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:
Confirmed
Status in cloud-init source package in Xenial:
Fix Committed
Status in cloud-init source package in Yakkety:
Confirmed
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.
Related bugs:
* bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
