On 32-bit sfdisk fails to parse the label-id if the MSB is set and thus generates a new one. We happen to be unlucky with our (i386) cloud image in that the original label-id has the MSB set. So when growpart run (which calls sfdisk), the disk ID is regenerated and subsequent boots fail because the kernel can't find the root device.
On 32-bit sfdisk fails to parse the label-id if the MSB is set and thus generates a new one. We happen to be unlucky with our (i386) cloud image in that the original label-id has the MSB set. So when growpart run (which calls sfdisk), the disk ID is regenerated and subsequent boots fail because the kernel can't find the root device.