Project

General

Profile

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 over 4 years ago. Updated over 4 years ago.

Status:
Released
Priority:
1
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
2.10.17
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
User visibility:
Effort required:
Priority:

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

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

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

Associated revisions

Revision 9b9bb343 (diff)
Added by Nicolas CHARLES over 4 years ago

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

Revision 95491b9c (diff)
Added by Nicolas CHARLES over 4 years ago

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

Revision f6c40c96
Added by Matthieu CERDA over 4 years ago

Merge pull request #922 from ncharles/bug_7154/agent_schedule_is_not_historised_so_we_can_t_know_what_was_the_agent_run_interval_in_the_past

Fixes #7154: Agent schedule is not historised, so we can't know what …

Revision 241a897a
Added by Matthieu CERDA over 4 years ago

Merge pull request #922 from ncharles/bug_7154/agent_schedule_is_not_historised_so_we_can_t_know_what_was_the_agent_run_interval_in_the_past

Fixes #7154: Agent schedule is not historised, so we can't know what …

History

#1

Updated by Nicolas CHARLES over 4 years ago

  • Target version changed from 2.11.14 to 2.10.17
#2

Updated by Nicolas CHARLES over 4 years ago

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

Updated by Nicolas CHARLES over 4 years ago

  • 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
#4

Updated by Nicolas CHARLES over 4 years ago

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

Updated by Matthieu CERDA over 4 years ago

#6

Updated by Nicolas CHARLES over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

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

Also available in: Atom PDF