This is as expected, the root partition in the registered image will not match the size of the disk that is deployed. It will be large enough to contain the root partition and provide some blank space. This is by design and allows VMs to be started with variable size disks. This is seen early in boot before cloud-init runs and because the disk from the image builder is smaller it will leave the gpt backup table in the middle of the deployed disk, but this is safe. One of the early cloud- init modules is growpart[1] and there's good documentation in the link for that module, but by default that module will grow the partition for the root filesystem to fill the disk and then grow the filesystem to fill that partition. In doing this the gpt backup table will be moved to a location correct for the root disk size at deployemtn; this is why you don't see the warning after reboot. In addition to giving flexibility for launching with different size root disks the user can instruct cloud-init not to resize the root filesystem[2][3] and instead use the unused space to create other partitions and filesystems[4].
[1] https://git.launchpad.net/cloud-init/tree/cloudinit/config/cc_growpart.py [2] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart [3] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#resizefs [4] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#disk-setup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828101 Title: [linux-azure] Disk Partition Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828101/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
