The bug is not cloud-init specific. I was able to create a yakkety VM with an extra partition not consuming the full size.
Running growpart on it behaves just the same. It actually resizes the disk, but there seems to be a new output/behavior in partx that lets it assume there is an error which causes the bad rc. => dry run looks good CHANGE: partition=2 start=11718656 old: size=1048576 end=12767232 new: size=5058527,end=16777183 # === old sfdisk -d === label: dos label-id: 0x6e682957 device: /dev/vda unit: sectors /dev/vda1 : start= 2048, size= 11716608, type=83, bootable /dev/vda2 : start= 11718656, size= 1048576, type=83 # === new sfdisk -d === label: dos label-id: 0x6e682957 device: /dev/vda unit: sectors /dev/vda1 : start= 2048, size= 11716608, type=83, bootable /dev/vda2 : start= 11718656, size= 5058527, type=83 => then without --dry-run failed [pt_update:1] pt_update /dev/vda 2 partx: partition and disk name do not match FAILED: pt_resize failed => but disk is actually updated Disk /dev/vda: 8 GiB, 8589934592 bytes, 16777216 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x6e682957 Device Boot Start End Sectors Size Id Type /dev/vda1 * 2048 11718655 11716608 5.6G 83 Linux /dev/vda2 11718656 16777182 5058527 2.4G 83 Linux ** Package changed: cloud-init (Ubuntu) => cloud-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587188 Title: [yakkety regression] does not grow partition any more To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1587188/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
