Project

General

Profile

Actions

Bug #7176

closed

Unexpected reports on "cron daemon" component of system techniques

Added by greg fr over 8 years ago. Updated over 8 years ago.

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

Description

In the standard directives, the "CRON Deamon" reports, on my system, two lines:

http://i.imgur.com/H0snByf.jpg

It's unexpected so it's orange. In that case it should be green, I think.

it's also probably the same for other directives.

(rudder server 3.0.8, client 3.0.8 on Debian 7.8)

Actions #1

Updated by Nicolas CHARLES over 8 years ago

  • Category set to System techniques
  • Priority changed from N/A to 3
  • Target version set to 3.0.9

This is obviously a bug in the system technique, that we should fix; unexpected should never happen
Thank you for the bug report !

Actions #2

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.9 to 3.0.10
Actions #3

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.10 to 3.0.11
Actions #4

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.11 to 3.0.12
Actions #5

Updated by Jonathan CLARKE over 8 years ago

  • Subject changed from More than 1 report answer could be better interpreted to Unexpected reports on "cron daemon" component of system techniques
Actions #6

Updated by Jonathan CLARKE over 8 years ago

  • Status changed from New to In progress
  • Assignee set to Jonathan CLARKE
Actions #7

Updated by Jonathan CLARKE over 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/789
Actions #8

Updated by Jonathan CLARKE over 8 years ago

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

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.12 and 3.1.5 which were released today.

Actions

Also available in: Atom PDF