Description of problem: resizefs cloud-init module (see /usr/lib/python2.6/site-packages/cloudinit/CloudConfig/cc_resizefs.py) always uses resize2fs (hardcoded) while trying to resize the root filesystem. If the root filesystem is EXT4, the following backtrace is printed while booting: loud-init start running: Mon, 10 Sep 2012 19:33:32 +0000. up 9.09 seconds found data source: DataSourceEc2 2012-09-10 15:33:32,869 - cc_resizefs.py[WARNING]: Failed to resize filesystem (['resize2fs', '/tmp/tmpAaw0hz']) 2012-09-10 15:33:32,871 - cc_resizefs.py[WARNING]: output=Couldn't find valid filesystem superblock. error=resize2fs 1.39 (29-May-2006) resize2fs: Filesystem has unsupported feature(s) while trying to open /tmp/tmpAaw0hz 2012-09-10 15:33:32,894 - __init__.py[WARNING]: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/cloudinit/CloudConfig/__init__.py", line 118, in run_cc_modules cc.handle(name, run_args, freq=freq) File "/usr/lib/python2.6/site-packages/cloudinit/CloudConfig/__init__.py", line 79, in handle [name, self.cfg, self.cloud, cloudinit.log, args]) File "/usr/lib/python2.6/site-packages/cloudinit/__init__.py", line 324, in sem_and_run func(*args) File "/usr/lib/python2.6/site-packages/cloudinit/CloudConfig/cc_resizefs.py", line 81, in handle util.subp(resize_cmd) File "/usr/lib/python2.6/site-packages/cloudinit/util.py", line 232, in subp raise _exc CalledProcessError: Command '['resize2fs', '/tmp/tmpAaw0hz']' returned non-zero exit status 1 2012-09-10 15:33:32,903 - __init__.py[ERROR]: config handling of resizefs, None, [] failed --- [root@test ~]# resize2fs /dev/root resize2fs 1.39 (29-May-2006) resize2fs: Filesystem has unsupported feature(s) while trying to open /dev/root Couldn't find valid filesystem superblock. [root@test ~]# resize4fs /dev/root resize4fs 1.41.12 (17-May-2010) The filesystem is already 26214400 blocks long. Nothing to do! --- My guess is that resizefs module should use resize4fs from e4fsprogs in RHEL5 derived distributions. Version-Release number of selected component (if applicable): Name : cloud-init Relocations: (not relocatable) Version : 0.6.3 Vendor: Fedora Project Release : 0.9.bzr532.el5 Build Date: Fri 20 Jul 2012 02:32:40 PM EDT Install Date: Mon 10 Sep 2012 10:57:52 AM EDT Build Host: buildvm-04.phx2.fedoraproject.org Group : System Environment/Base Source RPM: cloud-init-0.6.3-0.9.bzr532.el5.src.rpm Size : 645899 License: GPLv3 Signature : DSA/SHA1, Fri 20 Jul 2012 07:01:21 PM EDT, Key ID 119cc036217521f6 Packager : Fedora Project URL : http://launchpad.net/cloud-init Summary : Cloud instance init scripts Description : Cloud-init is a set of init scripts for cloud instances. Cloud instances need special scripts to run during initialization to retrieve and install ssh keys and to let the user run various scripts.
I believe this bug only affects RHEL5 distributions, RHEL6 isn't affected AFAIK.
Yes it seems e4fsprogs was a parallel installable version of e2fsprogs, as ext4 was only available as a technology preview on RHEL 5. Update coming up...
cloud-init-0.6.3-0.10.bzr532.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/cloud-init-0.6.3-0.10.bzr532.el5
Nice, thanks.
Package cloud-init-0.6.3-0.10.bzr532.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing cloud-init-0.6.3-0.10.bzr532.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-12871/cloud-init-0.6.3-0.10.bzr532.el5 then log in and leave karma (feedback).
cloud-init-0.6.3-0.10.bzr532.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.