** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Zesty)
Importance: Undecided => Medium
--
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/1692093
Title:
Cloud init is re-executing fs and disk setup during reboot
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
Bug description:
Cloud Provider: Azure
dpkg-query -W -f='${Version}' cloud-init output:
0.7.9-90-g61eb03fe-0ubuntu1~16.04.1
When the following is specified in cloud init it seems to be re-executing fs
and disk setup (even though run command does not seem to re run)
disk_setup:
/dev/sdc:
table_type: gpt
layout: true
overwrite: false
fs_setup:
- label: etcd_disk
filesystem: ext4
device: /dev/sdc1
extra_opts:
- "-F"
- "-E"
- "lazy_itable_init=1,lazy_journal_init=1"
mounts:
- - /dev/sdc1
- /var/lib/etcddisk
From cloud-init-output.log:
Cloud-init v. 0.7.9 running 'modules:final' at Mon, 15 May 2017 18:33:15
+0000. Up 64.24 seconds.
Cloud-init v. 0.7.9 finished at Mon, 15 May 2017 18:34:46 +0000. Datasource
DataSourceAzureNet [seed=/dev/sr0]. Up 155.34 seconds
Cloud-init v. 0.7.9 running 'init-local' at Tue, 16 May 2017 01:52:37 +0000.
Up 10.33 seconds.
Cloud-init v. 0.7.9 running 'init' at Tue, 16 May 2017 01:52:39 +0000. Up
12.06 seconds.
From cloud-init.log for the initial provision:
2017-05-15 18:32:46,820 - cc_disk_setup.py[DEBUG]: Creating file system
etcd_disk on /dev/sdc1
2017-05-15 18:32:46,820 - cc_disk_setup.py[DEBUG]: Using cmd:
/sbin/mkfs.ext4 /dev/sdc1 -L etcd_disk -F -E
lazy_itable_init=1,lazy_journal_init=1
2017-05-15 18:32:46,820 - util.py[DEBUG]: Running command ['/sbin/mkfs.ext4',
'/dev/sdc1', '-L', 'etcd_disk', '-F', '-E',
'lazy_itable_init=1,lazy_journal_init=1'] with allowed return codes [0]
(shell=False, capture=True)
2017-05-15 18:33:04,054 - util.py[DEBUG]: Creating fs for /dev/sdc1 took
17.237 seconds
and after reboot (cloud-init.log)
2017-05-16 01:52:40,245 - cc_disk_setup.py[DEBUG]: Creating file system
etcd_disk on /dev/sdc1
2017-05-16 01:52:40,246 - cc_disk_setup.py[DEBUG]: Using cmd:
/sbin/mkfs.ext4 /dev/sdc1 -L etcd_disk -F -E
lazy_itable_init=1,lazy_journal_init=1
2017-05-16 01:52:40,246 - util.py[DEBUG]: Running command ['/sbin/mkfs.ext4',
'/dev/sdc1', '-L', 'etcd_disk', '-F', '-E',
'lazy_itable_init=1,lazy_journal_init=1'] with allowed return codes [0]
(shell=False, capture=True)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1692093/+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
