[13:40] <Eighth_Doctor> falcojr: reminiscent to what we discussed several months back, I've proposed a change to rejigger the default network renderers: https://github.com/canonical/cloud-init/pull/1435
[13:40] <Eighth_Doctor> this is based on the patch I used for Fedora's cloud-init package: https://src.fedoraproject.org/rpms/cloud-init/blob/f0a6cf49bd20ccb145f6a7a1d5e94532931a7f8f/f/cloud-init-22.1-nm-default.patch
[13:41] <Eighth_Doctor> it's been validated with the Fedora 36 testing to ensure it works as intended, so I'm proposing it for upstream
[15:41] <Razva> hey. I've edited `/etc/cloud/cloud.cfg` and removed `growpart` and `resizefs`, then stopped the VM. After this I booted gParted live and reset. I then booted again in gParted, the partition had the correct (new) size. Finally I rebooted the VM and, after logging in, the partition got back to the incorrect (old) size. Upon rebooting into gParted, the partition had indeed the old size. So basically the partition grows each time the OS boots.
[15:41] <Razva> I tried this with the cloud-init drive removed from the VM, the result is the same.
[15:41] <Razva> can you please let me know what I'm doing wrong? Do I need to do anything else after editing the cfg?
[15:55] <minimal> Razva: you mean you removed "growpart" and "resizefs" from the "cloud_init_modules" section fo /etc/cloud/cloud.cfg?
[15:56] <minimal> did you try turning on cloud-init debugging so then /var/log/cloud-init.log will contain more details of what happens during boot (e.g. whether or not it runs the growpart and resizefs modules)
[15:58] <Razva> yes, I removed them from `modules`. Thanks for the log tip, I'll do it now.
[23:35] <amessyroom> is there a pastebin url that is used on this channel? Trying to use jinja templating in #cloud-config file but doesn't seem to work with cloud-init 19.4