Comment 11 for bug 1686514

Hi Scott,

As an additional test case I've tried to use the steps as described here to re-partition the ephemeral disk: https://wiki.ubuntu.com/AzureSwapPartitions.

Using your branch from this bug the sult is that it appears to fail to repartition but it does format/mount the disks. Here are my repro steps

 $ azure group create ubtest 'east us'

 $ azure vm create ubtest ubtest-1604 Linux --image-urn canonical:UbuntuServer:16.04-LTS:latest --admin-username azureuser --admin-password '<PASSWORD>' --nic-name ubtest-1604 --location "East US" --vnet-name "ubtest" --vnet-address-prefix "10.0.0.0/24" --vnet-subnet-name "ubtest" --vnet-subnet-address-prefix "10.0.0.0/24" --public-ip-name "ubtest" --public-ip-domain-name "ubtest" --custom-data ./customdata.txt -z 'Standard_L32s'

The customdata.txt file contains something like the following:

 #cloud-config
 disk_setup:
     ephemeral0:
         table_type: gpt
         layout: [66, [33, 82]]
         overwrite: True
 fs_setup:
     - device: ephemeral0.1
       filesystem: ext4
     - device: ephemeral0.2
       filesystem: swap
 mounts:
     - ["ephemeral0.1", "/mnt"]
     - ["ephemeral0.2", "none", "swap", "sw", "0", "0"]

.
.
Result with default 16.04 image: /mnt is not mounted and we see a failure in the cloud-init.log (attached).

Results with branch from this bug: /mnt and swap space are created, but the partition layout is not applied. So part1 is still type "Microsoft reserved" and only 120MB, and part2 is type "Microsoft basic data" and is a 5.5TB swap partition :)

Maybe there's something wrong with my cloud-config? Do I need to use a different layout format when table_type is 'gpt'?