Bug 109637 - Enh: add warning about removing contents on /var/log/rhr with "resolution" script
Summary: Enh: add warning about removing contents on /var/log/rhr with "resolution" sc...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: rhr2-tests
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rob Landry
QA Contact: Rob Landry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-10 15:20 UTC by Glen A. Foster
Modified: 2007-04-18 16:59 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-04-29 15:34:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Glen A. Foster 2003-11-10 15:20:17 UTC
Description of problem: It's certainly not a problem that the
resolution script removes the contents of /var/log/rhr/ when it
creates the RPM for submittal... but good U/I design generally
dictates that when data is about to be seriously modified, the user
receives _some_ notification it's about to happen and gets an
opportunity to abort the operation before it happens.


Version-Release number of selected component (if applicable):
# rpm -q rhr2
rhr2-0.9-14

Comment 1 Rob Landry 2003-11-10 20:09:10 UTC
added to CVS; will now prompt user ensuring they are aware that
/var/log/rhr will be removed after building the results package.

Comment 2 Glen A. Foster 2004-01-26 00:29:42 UTC
This fix doesn't show up in the 0.9-14.2 RPMs posted to Rob's people
page.  Is that intentional?

Comment 3 Rob Landry 2004-09-14 14:06:57 UTC
Yes and no; originally CVS was headed down the -15 route; since I
didn't want to introduce new packages in the middle and -15 wasn't
that well tested (turns out it's pretty busted) -14 was returned to
but unfortunately didn't inherit this change.  This has been added to
the -14 tree now.  I'll post new test packages later today.

Comment 4 Rob Landry 2005-04-14 16:52:38 UTC
Don't recall when initially added, but this is already in -17beta.


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