Project

General

Profile

Actions
Copy link

Bug #7154

closed

Agent schedule is not historised, so we can't know what was the agent run interval in the past

Bug #7154: Agent schedule is not historised, so we can't know what was the agent run interval in the past

Added by Nicolas CHARLES almost 11 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
2.10.17
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We are missing important historization data: agent schedule (on both node and global), so it prevents gathering relevant data about the past (for instance for advanced reporting module)

Subtasks 4 (0 open — 4 closed)

Bug #7161: Create a migration script for the database change for historization of global agent scheduleReleasedMatthieu CERDAActions
Bug #7213: Use tab to ident in debian/rules or else it failsReleasedMatthieu CERDAActions
Bug #7164: typo in the sql schema following a merge 2.11->3.0ReleasedFrançois ARMANDActions
Bug #7165: Typo in migration script, <<<<<<<<<<< HEAD remaining after a mergeReleasedMatthieu CERDAActions

Related issues 1 (0 open — 1 closed)

Related to Rudder - User story #3679: Make the agent run schedule configurable from 5 minutes to 6 hours, with configurable offset and splay timeReleasedNicolas CHARLESActions

Updated by Nicolas CHARLES almost 11 years ago Actions
Copy link
 #1

  • Target version changed from 2.11.14 to 2.10.17

Updated by Nicolas CHARLES almost 11 years ago Actions
Copy link
 #2

  • Related to User story #3679: Make the agent run schedule configurable from 5 minutes to 6 hours, with configurable offset and splay time added

Updated by Nicolas CHARLES almost 11 years ago Actions
Copy link
 #3

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/922

Updated by Nicolas CHARLES almost 11 years ago Actions
Copy link
 #4

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

Updated by Matthieu CERDA almost 11 years ago Actions
Copy link
 #5

Updated by Nicolas CHARLES almost 11 years ago Actions
Copy link
 #6

  • Related to Bug #7164: typo in the sql schema following a merge 2.11->3.0 added

Updated by Vincent MEMBRÉ almost 11 years ago Actions
Copy link
 #7

  • Related to deleted (Bug #7164: typo in the sql schema following a merge 2.11->3.0)

Updated by Vincent MEMBRÉ almost 11 years ago Actions
Copy link
 #8

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.17, 2.11.14, 3.0.9 and 3.1.2 which were released today.

Actions
Copy link

Also available in: PDF Atom