This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.12 --------------- cloud-init (0.6.3-0ubuntu1.12) precise-proposed; urgency=low
* debian/patches/lp-1269626-azure_new_instance.patch: fix handling of new instances on Windows Azure. Backport of fix from 14.04 (LP: #1269626). * debian/patches/lp-1292648-azure-format-ephemeral-new.patch: Azure, re-format ephemeral disk if necessary (LP: #1292648). -- Ben Howard <ben.how...@ubuntu.com> Tue, 18 Mar 2014 10:58:12 -0600 ** Changed in: cloud-init (Ubuntu Precise) 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/1292648 Title: [SRU] cloud-init should check/format Azure empheral disks each boot Status in Init scripts for use on cloud images: Fix Committed 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 Saucy: Fix Released Bug description: SRU Justification [IMPACT] Users on Windows Azure are guaranteed to have the ephemeral device as ext4 for the first boot. Subsequent boots may result in fuse mounted NTFS file system. [TEST CASE] Defined in comment 3. [Regression Potential] Low. This change is scope only to the Windows Azure datasource and the behavior complies with expected behavior of Windows Azure: the ephemeral disk is not durable between boots. From Microsoft documentation: > Because data on a resource disk may not be durable across reboots, it is often used by > applications and processes running in the virtual machine for transient and temporary > storage of data. It is also used to store page or swap files for the operating system. (See http://www.windowsazure.com/en-us/documentation/articles/storage-windows-attach-disk/) Even so, the change to Cloud-init is scope to only replace the ephemeral disk when the disk is 1) NTFS; 2) has a label of "Temporary Storage"; and 3) has no files on it. When the disk matches, cloud-init will turn the code paths for formating the ephemeral disk for that boot only. [ORIGINAL REPORT] On Windows Azure, the ephemeral disk should be treated as ephemeral per boot, not per instance. Microsoft has informed us that under the following conditions an ephemeral disk may disappear: 1. The user resizes the instance 2. A fault causes the instance to move from one physical host to another 3. A machine is shutdown and then started again Essentially, on Azure, the ephemeral disk is extremely ephemeral. Users who hit any of the above situations are discovering that /mnt is mount with their default NTFS file system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cloud-init 0.7.5~bzr964-0ubuntu1 [modified: usr/lib/python2.7/dist-packages/cloudinit/config/cc_disk_setup.py usr/lib/python2.7/dist-packages/cloudinit/config/cc_final_message.py usr/lib/python2.7/dist-packages/cloudinit/config/cc_seed_random.py usr/lib/python2.7/dist-packages/cloudinit/sources/DataSourceAzure.py usr/lib/python2.7/dist-packages/cloudinit/sources/DataSourceCloudSigma.py usr/lib/python2.7/dist-packages/cloudinit/sources/DataSourceSmartOS.py] ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Fri Mar 14 17:53:20 2014 PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1292648/+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