Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1201229 - cloud-init does not do the resize
Summary: cloud-init does not do the resize
Status: CLOSED DUPLICATE of bug 1197894
Alias: None
Product: Fedora
Classification: Fedora
Component: cloud-init
Version: 22
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Garrett Holmstrom
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F22BetaBlocker
TreeView+ depends on / blocked
Reported: 2015-03-12 11:23 UTC by Attila Fazekas
Modified: 2015-03-16 16:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-03-16 16:51:29 UTC
Type: Bug

Attachments (Terms of Use)

Description Attila Fazekas 2015-03-12 11:23:04 UTC
Description of problem:
After booting the cloud image the file system is not resized, even if it explicitly specified in the cloud config.

resize_rootfs: noblock
resize_rootfs: true

$ df -h
/dev/vda1       2.9G  444M  2.3G  17% /

The flavor m1.large (4) with 80GB disk.

Version-Release number of selected component (if applicable):

Expected results:
/dev/vda1 partition and filesystem is resized to the maximum available space.

Additional info:
The qcow2 file was converted to compat=0.10 version because the host is running el6, but it does not expected to cause this issue.

Comment 1 Garrett Holmstrom 2015-03-12 17:47:49 UTC
Which image and cloud did you encounter this with?

Comment 2 Garrett Holmstrom 2015-03-12 17:54:17 UTC
This could very well be caused by bug 1197894, which already blocks F22 beta.

Comment 3 Dan Mossor [danofsatx] 2015-03-16 16:51:29 UTC

*** This bug has been marked as a duplicate of bug 1197894 ***

Note You need to log in before you can comment on or make changes to this bug.