Description of problem:
After booting the cloud image the file system is not resized, even if it explicitly specified in the cloud config.
$ 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):
/dev/vda1 partition and filesystem is resized to the maximum available space.
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.
Which image and cloud did you encounter this with?
This could very well be caused by bug 1197894, which already blocks F22 beta.
*** This bug has been marked as a duplicate of bug 1197894 ***