First, reproduced and verified the mount was not succeeding. Then,
upgraded to the version in proposed and rebooted confirm that the disk
was mounted. Used the following cmd to boot an instance in azure with
the following cloud-config:
$ az vm create -n ci-test-1687712-$release -g $group --image $release_img
--data-disk-sizes-gb 8 --size Standard_DS2_v2 --ssh-key-value ~/.ssh/id_rsa.pub
--custom-data setup.cfg
$ cat setup.cfg
#cloud-config
disk_setup:
/dev/sdc:
table_type: gpt
layout: [[100, 83]]
fs_setup:
- cmd: mkfs -F -t %(filesystem)s -L %(label)s %(device)s
filesystem: ext4
device: /dev/sdc
partition: 1
label: repro
mounts:
- [/dev/sdc1, /repro]
* xenial (0.7.9-153-g16a7302f-0ubuntu1~16.04.1)
* yakkety (0.7.9-153-g16a7302f-0ubuntu1~16.10.1)
* zesty (0.7.9-153-g16a7302f-0ubuntu1~17.04.1)
Marking verification done.
** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-done-yakkety
verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687712
Title:
cc_disk_setup: fs_setup with cmd doesn't work
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1687712/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
