With cloud-init on Xenial from proposed (0.7.9-153-g16a7302f-0ubuntu1~16.04.1) I found the error message is gone, however, I do not see the disk when I do `ls -s /dev/disk/by-id/`, see below:
My steps:
$ az vm create -n cloud-init-test -g $my_group --image ubuntults --data-disk-sizes-gb 8 --size Standard_DS2_v2 --ssh-key-value ~/.ssh/id_rsa.pub
$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdc /dev/sdc1
$ ls -l /dev/disk/by-label/
total 0
lrwxrwxrwx 1 root root 10 Jun 20 22:57 cloudimg-rootfs -> ../../sda1
lrwxrwxrwx 1 root root 9 Jun 20 22:57 rd_rdfe_stable.161107-1031 -> ../../sr0
I am not sure if I am missing something or if there are better verification steps. In either case , this bug needs a formal SRU template with real test steps.
With cloud-init on Xenial from proposed (0.7.9- 153-g16a7302f- 0ubuntu1~ 16.04.1) I found the error message is gone, however, I do not see the disk when I do `ls -s /dev/disk/by-id/`, see below:
My steps: disk-sizes- gb 8 --size Standard_DS2_v2 --ssh-key-value ~/.ssh/id_rsa.pub
$ az vm create -n cloud-init-test -g $my_group --image ubuntults --data-
$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdc /dev/sdc1
$ cat /etc/cloud/ cloud.cfg. d/disk- setup.cfg
#cloud-config
fs_setup:
- special:
cmd: mkfs -t %(filesystem)s -L %(label)s %(device)s
filesystem: ext4
device: /dev/sdc1
label: repronew
$ ls -l /dev/disk/by-label/ stable. 161107- 1031 -> ../../sr0
total 0
lrwxrwxrwx 1 root root 10 Jun 20 22:57 cloudimg-rootfs -> ../../sda1
lrwxrwxrwx 1 root root 9 Jun 20 22:57 rd_rdfe_
I am not sure if I am missing something or if there are better verification steps. In either case , this bug needs a formal SRU template with real test steps.