Ubuntu 18.04, growpart and resizefs show disabled

[tom king]

In Ubuntu 18.04, the ext4 filesystem is not extended. cloud-init.log has these lines:

2018-05-14 21:15:24,908 - stages.py[DEBUG]: Running module growpart (<module 'cloudinit.config.cc_growpart' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py'>) with frequency always
2018-05-14 21:15:24,908 - handlers.py[DEBUG]: start: init-network/config-growpart: running config-growpart with frequency always
2018-05-14 21:15:24,908 - helpers.py[DEBUG]: Running config-growpart using lock (<cloudinit.helpers.DummyLock object at 0x7f67dea654e0>)
2018-05-14 21:15:24,908 - cc_growpart.py[DEBUG]: growpart disabled: mode=off
2018-05-14 21:15:24,908 - handlers.py[DEBUG]: finish: init-network/config-growpart: SUCCESS: config-growpart ran successfully
2018-05-14 21:15:24,908 - stages.py[DEBUG]: Running module resizefs (<module 'cloudinit.config.cc_resizefs' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_resizefs.py'>) with frequency always
2018-05-14 21:15:24,909 - handlers.py[DEBUG]: start: init-network/config-resizefs: running config-resizefs with frequency always
2018-05-14 21:15:24,909 - helpers.py[DEBUG]: Running config-resizefs using lock (<cloudinit.helpers.DummyLock object at 0x7f67dea65668>)
2018-05-14 21:15:24,922 - cc_resizefs.py[DEBUG]: Skipping module named resizefs, resizing disabled
2018-05-14 21:15:24,922 - handlers.py[DEBUG]: finish: init-network/config-resizefs: SUCCESS: config-resizefs ran successfully

lab@lab:/usr/lib/python3/dist-packages/cloudinit/config$ dpkg -l | grep cloud
ii cloud-guest-utils 0.30-0ubuntu5 all cloud guest utilities
ii cloud-image-utils 0.30-0ubuntu5 all cloud image management utilities
ii cloud-init 18.2-14-g6d48d265-0ubuntu1 all Init scripts for cloud instances
ii cloud-initramfs-copymods 0.40ubuntu1 all copy initramfs modules into root filesystem for later use
ii cloud-initramfs-dyn-netconf 0.40ubuntu1 all write a network interface file in /run for BOOTIF
ii cloud-initramfs-growroot 0.40ubuntu1 all automatically resize the root partition on first boot
ii cloud-utils 0.30-0ubuntu5 all metapackage for installation of upstream cloud-utils source

I've tried with mode auto and mode growpart in cc_growpart.py but with the same results.

I have compared to Ubuntu 16.04 which runs successfully, and I cannot find any difference that would disable both modules.

[Chad Smith (chad.smith)]

Thank you for filing a bug and making cloud-init better Tom. If possible please run "sudo cloud-init collect-logs" on the system in question so we can get a better understanding of the system config and user-config provided to this module. It will create a cloud-init.tar.gz in the current working directory that can be attached to this bug.

I'll set as Incomplete for the moment, please reset to New once the fulll logs/artifacts are attached.

[tom king (kingttx)]

Add log bundle.

[Scott Moser (smoser)]

Hi,
I've moved this over to cloud-init.
I'm interested in knowing what environment you're running this in.

1. How did you build/get this image? It looks like there is a NoCloud seed (run/result.json)
2. Where are you running the image?
3. What changes are made to /etc/cloud/cloud.cfg or /etc/cloud/cloud.cfg.d

A tar file of /var/lib/cloud/instance and /etc/cloud/cloud.cfg*

When you've answered these questions, please set the state back to 'New'
would be helpful.

Thanks.

[tom king (kingttx)]

1. How did you build/get this image? It looks like there is a NoCloud seed (run/result.json)
I built this by installing the OS and installing packages following this guide:
https://docs.openstack.org/image-guide/openstack-images.html

2. Where are you running the image?
VMware Integrated OpenStack

3. What changes are made to /etc/cloud/cloud.cfg or /etc/cloud/cloud.cfg.d
I've since deleted the self-built image and used a cloud image instead. I had enabled root in the cloud.cfg file and allowed passwords in the OpenSSH server config.

[tom king (kingttx)]

Add requested info and change status to New.

[Ryan Harper (raharper)]

> I've since deleted the self-built image and used a cloud image instead.

What cloud image are you using?

And are you still having issues ?

[tom king (kingttx)]

> What cloud image are you using?

https://cloud-images.ubuntu.com/bionic/current/

> And are you still having issues ?
I haven't retried a self-built image since modifying the cloud image to suit our needs.

[Launchpad Janitor (janitor)]

[Expired for cloud-init because there has been no activity for 60 days.]

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3181