Autotest free space verification check is insufficiently strict
Reported by
jrbarnette@chromium.org,
May 26 2016
|
||||||
Issue descriptionAutotest host verification includes a check that free space in the stateful partition is above a certain threshold. The principle driver for the space requirement is that there must be enough space in stateful to unpack a new 'stateful.tgz' with room to spare for testing. The space requirement is 700MB (.7Gb) A typical stateful.tgz unpacks >750MB. We need to make the free space requirement stricter. The minimum size should probably be raised to something like 900MB (.9GB).
,
Jun 2 2016
This isn't a test, and there are no failures. Yet. The issue is that it's possible that a DUT could finish testing and have (say) only 725GB free. It would then fail provisioning for lack of free space. That would look like a failure in the new build being provisioned, rather than a problem on the DUT.
,
Jun 6 2016
In theory, the fix is as easy as the patch shown below. However, in practice, that change could be bad for Rialto. We probably want to create a board-specific size configuration, similar to what we do for "kilo_inodes_required". That requires a little extra work. I'm not going to have time to tackle this right away, and there's no special expertise required. Dropping ownership, to allow someone else to take it on, if needed. Sample patch: diff --git a/global_config.ini b/global_config.ini index d24dff6..765937a 100644 --- a/global_config.ini +++ b/global_config.ini @@ -120,7 +120,7 @@ rpc_max_log_size_mb: 20 # Transfer RPC logs to a RPC logging server rpc_logserver: False # Minimum amount of disk space required for AutoTest in GB -gb_diskspace_required: 0.7 +gb_diskspace_required: 0.9 # Minmum number of i-nodes for stateful, in 1000 i-node units. kilo_inodes_required: 100 # Rialto has a small disk size, so reduce the required inodes for it.
,
Jun 11 2016
For an example of why this matters, please see bug 619156 . ... and yes, that means we should probably escalate action here. :-(
,
Jun 21 2016
Will find owner on product team.
,
Jun 22 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 29 2017
Dropping priority. This is an old issue, not sure how relevant. gwendal@ is this something you could take a look at?
,
May 11 2018
Still relevant |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by autumn@chromium.org
, Jun 2 2016