yahoo-eng-team team mailing list archive

[James Falcon <1879552@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3687

** Bug watch added: github.com/canonical/cloud-init/issues #3687
   https://github.com/canonical/cloud-init/issues/3687

** Changed in: cloud-init
       Status: Confirmed => Expired

-- 
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/1879552

Title:
  Azure: cloud-init skips formatting the resource disk (ephemeral0) when
  there is additional data disks' configuration in user-data

Status in cloud-init:
  Expired

Bug description:
  Deploying a bionic VM on Azure
  (Canonical:UbuntunServer:18.04-LTS:latest) with VM Size
  Standard_DS1_V2 and an additional datadisk  with the following config

  #cloud-config

  disk_setup:
    /dev/disk/azure/scsi1/lun0:
      table_type: gpt
      layout: True
      overwrite: True

  fs_setup:
    - device: /dev/disk/azure/scsi1/lun0
      partition: 1
      filesystem: ext4

  mounts:
   - [ /dev/disk/azure/scsi1/lun0, /datadisk1, "ext4", "defaults,nofail,discard", "0", "0" ]

  Expected Result:
  + Resource disk (ephemeral0) is formatted as ext4 and mounted to /mnt (which is what happens without attaching the data disk)

  Actual Result:
  + Resource disk is partitioned but not formatted, got mounted to /mnt as ntfs

  I used this command to create a VM with datadisk and passing in custom data
   az vm create -g <resource_group> -n vmname --image Canonical:UbuntuServer:18.04-LTS:latest --admin-username adminuser --ssh-key-value @/home/user/.ssh/key.pub --boot-diagnostics-storage storage_account --size Standard_DS1_V2 --custom-data ./customdata.yml --data-disk-sizes-gb 32

  I have attached the cloud-init log and the custom data

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1879552/+subscriptions