Bug 979240 - kdump saved vmcore didnt used system timezone
kdump saved vmcore didnt used system timezone
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kexec-tools (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: WANG Chao
Red Hat Kernel QE team
Depends On:
  Show dependency treegraph
Reported: 2013-06-27 23:34 EDT by Xiaoqing Wei
Modified: 2015-02-08 16:44 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-14 09:34:50 EDT
Type: Bug
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 Xiaoqing Wei 2013-06-27 23:34:42 EDT
Description of problem:

setting the machine to CST timezone then trigger a kdump, the dir under /var/crash is not named using CST timezone

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


Steps to Reproduce:
1. install a host using ks and set timezone to below
grep -i time /root/anaconda-ks.cfg 
# System timezone
timezone Asia/Shanghai --isUtc 
2. trigger a kdump

Actual results:
# ll /var/crash
total 0
drwxr-xr-x. 2 root root 42 Jun 26 18:22
drwxr-xr-x. 2 root root 42 Jun 27 11:04
the FS timestamp using system timezone            ^^^^^^
                                                  the folders isn't, so the kexecing kernel didn't used the system timezone.

Expected results:

tested on a rhel6 machine, kexecing kernel used system timezone

[root@dhcp-10-30 ~]# grep -i time /root/anaconda-ks.cfg 
timezone --utc Asia/Shanghai
[root@dhcp-10-30 ~]# ll /var/crash/
total 4
drwxr-xr-x. 2 root root 4096 Jun 28 11:20
[root@dhcp-10-30 ~]# uname -r

Additional info:
Comment 2 WANG Chao 2013-10-14 09:34:50 EDT
We have fixed it in kexec-tools-2.0.4-7. So I'm closing this bz. Feel free to reopen it if you meet this issue again.

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