the cloud images have traditionally had a 1.4G filesystem.
it seems that that has recently shrunk to 1G. that, along with some general bloat has caused failure of maas image build process that is being addressed at https://code.launchpad.net/~rcj/maas-images/ppc64el/+merge/243667 .
i'm not sure what the reason was for shrinking the filesystme in the .tar.gz files.
reproduce / showing it is easy:
$ mirror=http://cloud-images.ubuntu.com/daily/server
$ for r in trusty utopic vivid; do wget $mirror/$r/current/$r-server-cloudimg-amd64.tar.gz; done
$ for i in *.tar.gz; do echo === $i ==; tar -tvzf $i | grep .img$ ; done
=== trusty-server-cloudimg-amd64.tar.gz ==
-rw-r--r-- root/root 1476395008 2015-01-23 00:43 trusty-server-cloudimg-amd64.img
=== utopic-server-cloudimg-amd64.tar.gz ==
-rw-r--r-- root/root 1476395008 2015-01-22 03:34 utopic-server-cloudimg-amd64.img
=== vivid-server-cloudimg-amd64.tar.gz ==
-rw-r--r-- root/root 995098624 2015-01-23 02:19 vivid-server-cloudimg-amd64.img
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/
To change the source package that this bug is filed about visit https:/
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]