Ubuntu 18.04, growpart and resizefs show disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Undecided
|
Unassigned |
Bug Description
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.
2018-05-14 21:15:24,908 - handlers.py[DEBUG]: start: init-network/
2018-05-14 21:15:24,908 - helpers.py[DEBUG]: Running config-growpart using lock (<cloudinit.
2018-05-14 21:15:24,908 - cc_growpart.
2018-05-14 21:15:24,908 - handlers.py[DEBUG]: finish: init-network/
2018-05-14 21:15:24,908 - stages.py[DEBUG]: Running module resizefs (<module 'cloudinit.
2018-05-14 21:15:24,909 - handlers.py[DEBUG]: start: init-network/
2018-05-14 21:15:24,909 - helpers.py[DEBUG]: Running config-resizefs using lock (<cloudinit.
2018-05-14 21:15:24,922 - cc_resizefs.
2018-05-14 21:15:24,922 - handlers.py[DEBUG]: finish: init-network/
lab@lab:
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-
ii cloud-initramfs
ii cloud-initramfs
ii cloud-initramfs
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.
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.