Project

General

Profile

Actions

Bug #7741

closed

date of report may be invalid on windows

Added by Nicolas CHARLES almost 9 years ago. Updated over 8 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On a windows system hosted on a linux system, the timezone may wreak havoc on the system, as i get reports with "16:10:39+0:00" in the report, when I'm actually +1:00
The command
"{0:HH:mm:sszzz}" -f (get-date) returns the proper value
16:11:06+01:00

(see http://stackoverflow.com/questions/11035905/powershell-display-current-time-with-time-zone )

Actions #1

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #2

Updated by Nicolas CHARLES almost 9 years ago

  • Status changed from New to In progress
Actions #3

Updated by Nicolas CHARLES almost 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/859
Actions #5

Updated by Nicolas CHARLES almost 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #6

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.19, 3.0.14, 3.1.8 and 3.2.1 which were released today.

Actions

Also available in: Atom PDF