Utah appear to be adding significant content for minimal virtual server installations for raring smoke tests. Whilst a fresh local minimal virtual installation of amd64 server takes up roughly 611MB the reported installation size using utah is 964MB which is nearly 50% offset to the correct value.
Please see comment #10 for further information as to what could add to the contents in preseeded installations required for utah.
Originally it was with i386 but from 20121209 the amd64 installations are also reporting larger than the expected maximum for the daily smoke tests.
i386 installations are reporting 885560 against the expected maximum of 870400
amd64 installations are showing 964812 against the expected maximum of 912656
i386 server (20121207) minimal virtual installations for raring with utah installation are reporting an installation size of 885560 against the expected maximum of 870400. The size was below the expected max until 20121206 for i386 server images and the bloating only happened with 20121207 i386 server images. For amd64 images the size was below the expected until 20121208 and the bloating only happened with 20121209 images
The corresponding test code is located,
http://bazaar.launchpad.net/~ubuntu-server-dev/utah/server-tests-quantal/view/head:/testsuites/minimal-virtual/test_install_size/test.py
The failure is
======================================================================
FAIL: testInstallSize (__main__.MinimalVirtualTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "test.py", line 48, in testInstallSize
self.assertTrue( used < max_install_size, "Used: %s" % (used))
AssertionError: Used: 885560
The impacted job is,
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-i386-smoke-minimal-virtual/20/
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1087630
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.