Cloud-init is always fun to debug :-). It will probably require some playing with to get a pattern down.
There is perhaps a way to get it to re-check and grow every reboot if you adjust/override the module frequency, deleting the module semaphore in /var/lib/cloud/sem or worst case clearing the metadata via 'cloud-init clear' or deleting the /var/lib/cloud. On Mon, Oct 11, 2021 at 3:07 AM Wido den Hollander <w...@widodh.nl> wrote: > > > On 10/10/21 10:35 AM, Ranjit Jadhav wrote: > > Hello folks, > > > > I have implemented cloudstack with Xenserver Host. The template has been > > made out of VM with basic centos 7 and following package installed on it > > ------------------------ > > sudo yum -y cloud-init > > sudo yum -y install cloud-utils-growpart > > sudo yum -y install gdisk > > ------------------------ > > > > After creating new VM with this template, root disk is created as per > size > > mention in template or we are able to increase it at them time of > creation. > > > > But later when we try to increase root disk again, it increases disk > space > > but "/" partiton do not get autoresize. > > > > As far as I know it only grows the partition once, eg, upon first boot. > I won't do it again afterwards. > > Wido > > > > > Following parameters were passed in userdata > > ------------------------ > > #cloud-config > > growpart: > > mode: auto > > devices: ["/"] > > ignore_growroot_disabled: true > > ------------------------ > > > > Thanks & Regards, > > Ranjit > > >
