Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2470
** Bug watch added: github.com/canonical/cloud-init/issues #2470 https://github.com/canonical/cloud-init/issues/2470 ** Changed in: cloud-init Status: Triaged => Expired -- 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/1351821 Title: cloud-init resource disk handling conflicts with waagentlinux Status in cloud-init: Expired Bug description: While running Ubuntu 14.04 Trusty on Microsoft Azure, I got the fstab mangling bug described here: * http://askubuntu.com/questions/405442/how-can-i-disable-cloud-init This happened because the ResourceDisk.MountPoint=/tmp option was set in the /etc/waagent.conf file, and this line was in the /etc/fstab file: /dev/sdb1 /tmp ext4 defaults,noauto 0 2 From a deallocated start only, cloud-init incorrectly rewrites the resource disk line to this: /dev/sdb1 /mnt auto defaults,nobootwait,comment=cloudconfig 0 2 Reformatting behavior also seems to be irregular. Sometimes the resource disk is mounted as NTFS. Sometimes a double mount happens like this: # mount /dev/sdb1 on /tmp type ext4 (rw) /dev/sdb1 on /mnt type ext4 (rw,_netdev) Expected behavior is: 1. Features provided by the Windows Azure Agent for Linux are not overridden by cloud-init. 2. The /etc/fstab file is never changed after VM creation. 3. The resource disk is not forced onto /mnt. 4. The resource disk is unconditionally reformatted to ext4 at system start, preferably with the ^has_journal option for maximum performance. Trying to keep it intact across reboots is inconsistent with its purpose and most of the pertinent documentation. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1351821/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
