Bug 158635 - timestamp logs
timestamp logs
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: ispec (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Greg Nichols
Richard Li
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-05-24 10:17 EDT by Patrick C. F. Ernzer
Modified: 2008-07-17 18:04 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-17 18:04:14 EDT
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 Patrick C. F. Ernzer 2005-05-24 10:17:40 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Fedora/1.0.4-2 Firefox/1.0.4

Description of problem:
As a certification run can take a long time, we should really tiomestamp all logs

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. start certification run before leaving for lunch
2. come back from lunch
3. wonder when which logged step was taken

Actual Results:  no idea what happened when

Expected Results:  timestamps in logs

Additional info:

if we add this, we really also should have a setting for the timezone. Failing that we should use UTC timestamps and not eastern standard time as thet is rather useless for the other 23 timezones. (yes, I know I always nag that the world does not run on Eastern time)

We should also have --utc in the timezone line of the kickstart file
Comment 2 Rob Landry 2008-07-17 18:04:14 EDT
rhr2 has been deprecated, closing these remaining bugs as WONTFIX.  Future bugs
against the "hts" test suite should be opened agains the "Red Hat Hardware
Certification Program" product selecting either "Test Suite (harness)" or "Test
Suite (tests)" components.

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