Project

General

Profile

Bug #7739

Invalid reporting on windows for clockconfiguration if Hardware Clock is not set

Added by Nicolas CHARLES over 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Category:
Techniques
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

On windows, if the Synchronize the system clock periodically with the hardware clock is untick, we get unknown report
No synchronization with the hardware clock was requested This message was generated by agent.
The hardware clock is automatically synchronized with the NTP time on Windows This message was generated by agent.

#1

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to In progress
#2

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/837
#3

Updated by Nicolas CHARLES over 5 years ago

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

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.18, 3.0.13, 3.1.6 and 3.2.0 which were released today.

Also available in: Atom PDF