Project

General

Profile

Actions

Bug #7739

closed

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

Bug #7739: Invalid reporting on windows for clockconfiguration if Hardware Clock is not set

Added by Nicolas CHARLES over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
N/A
Assignee:
Jonathan CLARKE
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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.

Updated by Nicolas CHARLES over 10 years ago Actions #1

  • Status changed from New to In progress

Updated by Nicolas CHARLES over 10 years ago Actions #2

  • 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

Updated by Nicolas CHARLES over 10 years ago Actions #3

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

Updated by Vincent MEMBRÉ over 10 years ago Actions #4

  • 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.

Actions

Also available in: PDF Atom