Back to bug 1411100

Who When What Removed Added
Shirly Radco 2017-01-08 12:01:23 UTC Target Milestone --- ovirt-4.1.1
Shirly Radco 2017-01-08 12:19:14 UTC Blocks 1397833 1402901
Doron Fediuck 2017-01-09 09:18:11 UTC CC dfediuck, sradco
Flags needinfo?(sradco)
Shirly Radco 2017-01-09 11:17:28 UTC Flags needinfo?(sradco)
Yedidyah Bar David 2017-01-11 15:50:50 UTC Link ID oVirt gerrit 70025
Status NEW POST
Red Hat Bugzilla Rules Engine 2017-01-11 15:50:56 UTC Flags planning_ack? planning_ack+
Yaniv Kaul 2017-01-12 13:59:03 UTC Severity unspecified medium
Yaniv Lavi 2017-02-22 11:21:00 UTC CC ydary
Yaniv Kaul 2017-02-27 14:35:17 UTC Target Milestone ovirt-4.1.1 ovirt-4.2.0
Red Hat Bugzilla Rules Engine 2017-02-27 14:35:24 UTC Flags ovirt-4.1? ovirt-4.2?
Yedidyah Bar David 2017-04-05 07:32:25 UTC Status POST MODIFIED
Doc Type If docs needed, set a value Enhancement
Yedidyah Bar David 2017-04-05 07:45:03 UTC Keywords FutureFeature
Doc Text From now on, all timestamp records for otopi-based tools logs - including engine-setup, host-deploy, hosted-engine --deploy - will contain a time zone to ease correlation between logs on the Manager and hosts. They will also now include the fraction of a second. Previously they contained a timestamp without a time zone and fraction of a second, for example:

2017-04-03 09:56:58 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN

From now on there will always be a comma and fraction of second after the seconds part, and a timezone identifier at the end of the timestamp part, for example:

2017-04-05 10:41:08,500+0300 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN
Summary Change timestamp format to include timezone for logs [RFE] Change timestamp format to include timezone for logs
Lukas Svaty 2017-05-03 08:19:26 UTC CC lsvaty
QA Contact pstehlik pkubica
Flags testing_ack? testing_ack+
Red Hat Bugzilla Rules Engine 2017-05-03 08:19:33 UTC Flags ovirt-4.2? ovirt-4.2+
Sandro Bonazzola 2017-05-04 13:46:07 UTC CC rhev-integ-dev
Sandro Bonazzola 2017-06-29 10:15:01 UTC Priority unspecified medium
Gil Klein 2017-07-27 09:32:33 UTC Status MODIFIED ON_QA
Sandro Bonazzola 2017-07-31 05:40:18 UTC Target Release --- 1.7.0
Lukas Svaty 2017-08-23 12:35:34 UTC QA Contact pkubica smacko
samuel macko 2017-08-28 10:48:02 UTC Status ON_QA VERIFIED
Gil Klein 2017-09-06 16:07:29 UTC CC gklein
Flags testing_plan_complete-
Tahlia Richardson 2017-11-02 00:47:52 UTC CC trichard
Doc Text From now on, all timestamp records for otopi-based tools logs - including engine-setup, host-deploy, hosted-engine --deploy - will contain a time zone to ease correlation between logs on the Manager and hosts. They will also now include the fraction of a second. Previously they contained a timestamp without a time zone and fraction of a second, for example:

2017-04-03 09:56:58 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN

From now on there will always be a comma and fraction of second after the seconds part, and a timezone identifier at the end of the timestamp part, for example:

2017-04-05 10:41:08,500+0300 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN
From now on, all timestamp records for otopi-based tools logs (including engine-setup, host-deploy, and hosted-engine --deploy) will contain a time zone to ease correlation between logs on the Manager and hosts. They will also now include the fraction of a second. Previously they contained a timestamp without a time zone and fraction of a second, for example:

2017-04-03 09:56:58 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN

From now on there will always be a comma and fraction of a second after the seconds part, and a timezone identifier at the end of the timestamp part, for example:

2017-04-05 10:41:08,500+0300 DEBUG otopi.context context.dumpEnvironment:760 ENVIRONMENT DUMP - BEGIN
Sandro Bonazzola 2017-12-20 11:05:36 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2017-12-20 06:05:36 UTC
Gil Klein 2019-04-28 13:06:25 UTC CC gklein

Back to bug 1411100