Bug 114226 - Need to ensure adequate space in /var/log/rhr/tests for prep-phase
Need to ensure adequate space in /var/log/rhr/tests for prep-phase
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: rhr2-tests (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Rob Landry
Rob Landry
Depends On:
  Show dependency treegraph
Reported: 2004-01-24 14:14 EST by Glen A. Foster
Modified: 2007-04-18 13:02 EDT (History)
0 users

See Also:
Fixed In Version: RHBA-2005-871
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-12-20 10:36:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Glen A. Foster 2004-01-24 14:14:57 EST
Description of problem: I was running the CORE test on a couple of
systems and noticed that if a CORE test fails in a previous run and
fills up / (it _can_ happen :) the next runs of CORE will fail --
because there's not enough space for the logfiles and/or the rpmbuild.

I think the prep-phase, at least for CORE (if not all tests) should
look for some minimal amount of free space in the prep phase.

Version-Release number of selected component (if applicable):
# rpm -q rhr

How reproducible: very and easily

Steps to Reproduce:
1. Fill the filesystem for /usr/src/redhat and/or /var/log to 100%
2. Install rhr2 RPMs
3. Configure and run the CORE test
Actual results: failure due to lack of space

Expected results: prep phase should find such a requirement
Comment 1 Rob Landry 2004-07-22 10:34:57 EDT
should be addressed in 0.9-14.8k available on
Comment 2 Red Hat Bugzilla 2005-12-20 10:36:12 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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