I think this is a matter of bug 1411582 actually not having been SRU'd correctly. $ lsb_release -sc trusty $ dpkg-query --show cloud-init cloud-init 0.7.5-0ubuntu1.19 $ dpkg -L cloud-init | grep udev $ dpkg -L cloud-init | grep udev || echo no files named udev no files named udev
I also checked that the version that was marked as SRU'd in (0.7.5-0ubuntu1.8) does not have any udev files. So it seems that it just never got in, versus having regressed since 0.7.5-0ubuntu1.8. $ wget https://launchpad.net/ubuntu/+archive/primary/+files/cloud-init_0.7.5-0ubuntu1.8_all.deb $ dpkg -c cloud-init_0.7.5-0ubuntu1.8_all.deb | grep udev || echo no files named udev no files named udev ** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Yakkety) Importance: High Status: Confirmed ** Also affects: cloud-init (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Yakkety) Status: Confirmed => Fix Released ** No longer affects: cloud-init (Ubuntu Yakkety) ** No longer affects: cloud-init (Ubuntu Xenial) ** Changed in: cloud-init (Ubuntu Trusty) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Trusty) Status: New => Confirmed -- 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 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 Wily: 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/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : [email protected] Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
