Bug 1391381 - [RFE] Use UTC time for logging files in engine
Summary: [RFE] Use UTC time for logging files in engine
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ovirt-4.2.0
: ---
Assignee: Martin Perina
QA Contact: Aleksei Slaikovskii
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-03 08:28 UTC by Martin Perina
Modified: 2017-06-15 08:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-15 08:48:44 UTC
oVirt Team: Infra
mperina: ovirt-4.2?
mperina: planning_ack?
mperina: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 66016 0 master MERGED engine: Use named formatters for log config 2016-11-21 20:44:41 UTC
oVirt gerrit 66017 0 master MERGED engine: Add time zone to log records 2016-11-21 20:44:48 UTC
oVirt gerrit 66018 0 master ABANDONED engine: Use UTC time for log records 2017-06-20 07:23:00 UTC
oVirt gerrit 67161 0 master MERGED core: Introduce logutils module 2017-02-13 15:57:21 UTC
oVirt gerrit 67162 0 master MERGED tools: Add time zone to log records 2017-02-13 15:57:18 UTC

Description Martin Perina 2016-11-03 08:28:16 UTC
Description of problem:

Currently all logging files in engine use local time zone for log record times, which could make hard to link log files among engine and hosts in different time zones. The solution is to use UTC time in all log files.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Martin Perina 2016-12-01 13:49:17 UTC
Moving to 4.2 as we will not be able to change logging time zone in 4.1

Comment 2 Martin Perina 2017-06-15 08:48:44 UTC
Closing as NOTABUG, time zone changes will be performed in ElasticSearch as mentioned in BZ1390674


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