Project

General

Profile

Actions
Copy link

Bug #3132

closed

Technique 'Time settings': Reporting is invalid

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

Status:
Rejected
Priority:
2
Assignee:
Matthieu CERDA
Category:
Techniques
Target version:
2.6.11
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On a CentOS 5 64, the reporting sometimes fails on the Hardware clock (RTC)

2013-01-02 18:47     result_success     Configure Time Settings     Corporate Security Policy     Hardware clock (RTC)     -     It is not yet time to synchronize the hardware clock with the NTP time. Skipping...
2013-01-02 18:47     result_success     Configure Time Settings     Corporate Security Policy     Hardware clock (RTC)     -     The hardware clock has been synchronized with the NTP time

It seems it happens only on Centos5 (debian 5 and 6 are ok, as well as sles10-sp2)

Actions
Copy link
 #1

Updated by Matthieu CERDA almost 12 years ago

  • Target version changed from 2.3.10 to 2.3.11
Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 12 years ago

  • Project changed from Rudder to 24
  • Category deleted (Techniques)
Actions
Copy link
 #3

Updated by Matthieu CERDA over 11 years ago

  • Target version changed from 2.3.11 to 2.3.12
Actions
Copy link
 #4

Updated by Matthieu CERDA over 11 years ago

  • Target version changed from 2.3.12 to 2.3.13
Actions
Copy link
 #5

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.3.13 to 84
Actions
Copy link
 #6

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 84 to 2.4.7
Actions
Copy link
 #7

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions
Copy link
 #8

Updated by Matthieu CERDA about 11 years ago

  • Category set to Techniques
  • Status changed from New to In progress
  • Assignee set to Matthieu CERDA
  • Priority changed from 5 (lowest) to 2

Changing priority to 2, reason:

Working on this.

Actions
Copy link
 #9

Updated by Matthieu CERDA about 11 years ago

  • Status changed from In progress to Discussion
  • Assignee changed from Matthieu CERDA to Nicolas CHARLES

Actually, this is VERY surprising as the definition of the report is:

                (!windows.!ntp_hwclock_sync_error.!ntp_hwclock_synced)::
                        "@@ntpConfiguration@@result_success@@&TRACKINGKEY&@@Hardware clock (RTC)@@None@@$(g.execRun)##$(g.uuid)@#It is not yet time to synchronize the hardware clock with the NTP time. Skipping...";

                ntp_hwclock_synced::
                        "@@ntpConfiguration@@result_success@@&TRACKINGKEY&@@Hardware clock (RTC)@@None@@$(g.execRun)##$(g.uuid)@#The hardware clock has been synchronized with the NTP time";

The class ntp_hwclock_synced is triggered by an ifelapsed, are you sure that you did not trigger this during testing by nuking locks via cf-agent -K ?

Actions
Copy link
 #10

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions
Copy link
 #11

Updated by Jonathan CLARKE about 11 years ago

  • Assignee changed from Nicolas CHARLES to Matthieu CERDA

Apparently there may be other reporting bugs in this Technique - please test thoroughly and fix all issues!

Actions
Copy link
 #12

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.9 to 2.4.10
Actions
Copy link
 #13

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.10 to 2.4.11
Actions
Copy link
 #14

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.11 to 2.4.12
Actions
Copy link
 #15

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.12 to 2.4.13
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.4.13 to 2.6.11

Since Support for 2.4 branch is over, retargeting this issue to 2.6

Actions
Copy link
 #17

Updated by Jonathan CLARKE almost 11 years ago

  • Status changed from Discussion to Rejected

Given this definition of the reports, this bug is simply impossible:

                (!windows.!ntp_hwclock_sync_error.!ntp_hwclock_synced)::
                        "@@ntpConfiguration@@result_success@@&TRACKINGKEY&@@Hardware clock (RTC)@@None@@$(g.execRun)##$(g.uuid)@#It is not yet time to synchronize the hardware clock with the NTP time. Skipping...";

                ntp_hwclock_synced::
                        "@@ntpConfiguration@@result_success@@&TRACKINGKEY&@@Hardware clock (RTC)@@None@@$(g.execRun)##$(g.uuid)@#The hardware clock has been synchronized with the NTP time";

Rejecting. Please re-open if this is not the case (but we'll have to consider it as a CFEngine bug, then).

Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 10 years ago

  • Subject changed from Reporting in the Time settings technique is invalid to Reporting in 'Time settings' Technique is invalid
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 10 years ago

  • Subject changed from Reporting in 'Time settings' Technique is invalid to Technique 'Time settings': Reporting is invalid
Actions
Copy link
 #20

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 24 to Rudder
  • Category changed from Techniques to Techniques
Actions
Copy link

Also available in: Atom PDF