This bug was fixed in the package cloud-init -
0.7.9-231-g80bf98b9-0ubuntu1
---------------
cloud-init (0.7.9-231-g80bf98b9-0ubuntu1) artful; urgency=medium
* New upstream snapshot.
- tests: remove 'yakkety' from releases as it is EOL.
- systemd: make systemd-fsck run after cloud-init.service (LP: #1691489)
- tests: Add initial tests for EC2 and improve a docstring.
- locale: Do not re-run locale-gen if provided locale is system default.
- archlinux: fix set hostname usage of write_file.
[Joshua Powers] (LP: #1705306)
- sysconfig: support subnet type of 'manual'.
- Drop rand_str() usage in DNS redirection detection
[Bob Aman] (LP: #1088611)
-- Scott Moser <smo...@ubuntu.com> Mon, 31 Jul 2017 09:47:34 -0400
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => 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/1691489
Title:
fstab entries written by cloud-config may not be mounted
Status in cloud-init:
Confirmed
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Confirmed
Status in cloud-init source package in Yakkety:
Confirmed
Status in cloud-init source package in Zesty:
Confirmed
Status in cloud-init source package in Artful:
Fix Released
Bug description:
As reported in bug 1686514, sometimes /mnt will not get mounted when
re-delpoying or stopping-then-starting a Azure vm of L32S. This is
probably a more generic issue, I suspect shown due to the speed of
disks on these systems.
Related bugs:
* bug 1686514: Azure: cloud-init does not handle reformatting GPT partition
ephemeral disks
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1691489/+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
