Bug 807414 - kdump test fails after switchting to summer time / daylight saving time
Summary: kdump test fails after switchting to summer time / daylight saving time
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Test Suite (tests)
Version: 6.1
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: Caspar Zhang
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-27 17:45 UTC by Rainer Koenig
Modified: 2013-07-03 07:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-17 17:18:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Rainer Koenig 2012-03-27 17:45:33 UTC
Description of problem:
Germany switched to summer time (CEST) last weekend. Last week I performed 32-bit kdump tests on a test system and they passed. Today I performed the same tests with 64-bit and I failed. 

Version-Release number of selected component (if applicable):
Actual version of v7 testsuite

How reproducible:
always

Steps to Reproduce:
1. Install RHEL 6.2
2. Set HW clock to UTC and time zone to Europe/Berlin
3. Perform local kdump test
  
Actual results:
The test fails. The logs say, that no crashdump in a good time window could be found in /var/crash. 

Expected results:
kdump should work, regardless of the time and timezone settings.

Additional info:
Looking into /var/crash shows that the crashdump file is always 1 hour advanced to the real time.

Meanwhile I managed to pass the test with the following time settings:
- System clock is running on UTC
- System time zone is GMT-1h.

Looks like the change to summertime was messing things up. ;-)

Comment 1 Caspar Zhang 2012-07-18 07:44:23 UTC
Hi Rainer, is this still an issue? IIRC, the problem should no longer exist several hours later after switched to summer time.

Comment 2 Rob Landry 2012-08-06 19:07:38 UTC
Hrm,  I'm pretty certain nothing in v7 is daylight aware.  But it's worth confirming the issue does self resolve after a few hours or is there a period of time (days weeks months) where the various time zones being at different offsets continues to effect the test?


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