Verified on MOS9.0 (build 232) -
I've created 2 instances from this new image:
with root_gb == 0 - image(disk) size was grown, but we still have the same size for partition and fs, so growpart/resize2fs didn't apply
Details: http://pastebin.com/WJuGcUY9
So, my current understanding, that if we add more packages to this image in future and boot instances with flavor where disk == "0" we will get the same situation with disk space.
I guess, in this case (root_gb == 0) we should have "growpart/resize2fs" in this image in initrd.
Verified on MOS9.0 (build 232) -
I've created 2 instances from this new image:
with root_gb == 0 - image(disk) size was grown, but we still have the same size for partition and fs, so growpart/resize2fs didn't apply pastebin. com/WJuGcUY9
Details: http://
with root_gb == 1 - image(disk) /partition/ fs were increased pastebin. com/A6BBZW1Z
Details: http://
So, my current understanding, that if we add more packages to this image in future and boot instances with flavor where disk == "0" we will get the same situation with disk space. resize2fs" in this image in initrd.
I guess, in this case (root_gb == 0) we should have "growpart/