https://bugzilla.novell.com/show_bug.cgi?id=868184 https://bugzilla.novell.com/show_bug.cgi?id=868184#c3 Sven Michels <s.michels@external.telekom.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |s.michels@external.telekom. | |de --- Comment #3 from Sven Michels <s.michels@external.telekom.de> 2014-03-17 12:58:16 UTC --- Hi, i was the inital reporter of the problem. Let me give you some background why this popped up at all: We want to use SLES/SUSE Images on our OpenStack Service. When we first started using images from suse studio, we noticed that the growpart/resize filesystem feature doesn't work. So if you create an image with a 2GB partition and start it on a flavor with 10GB root disk, the root disk stays at 2GB. You can, of course, try to reclaim the space by yourself later, but thats not what we intent to have. We want to have the same feature of "auto growing" across all images. When playing around with a latest version of SUSE Images, the problem was still there. So i tried to fix it by myself adding the necessary stuff to the image (using overlaying archives or modify scripts afterwards). After adding the growpart stuff and run some tests it looked fine so far. But when i ported that one back to the base image, it stopped working. Reason was as described: the stages of cloud init where not executed. I'll try to rebuild an image with your "fixes", but it leaves me at the stage that i think this should work without such modifications. At all its a bit disappointing that suse studio does have an option/state like "the partition will grow to the full size of the disk later" when it simply doesn't work at all (nor has the feature at all.). So, i'll come back to this after some more tests. Best regards, Sven -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.