Project

General

Profile

Actions
Copy link

Bug #7161

closed

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

Create a migration script for the database change for historization of global agent schedule

Added by Nicolas CHARLES about 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Matthieu CERDA
Category:
Packaging
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

In parent ticket, we changed the database schema
This ticket is to create the migration script

Subtasks 1 (0 open — 1 closed)

Bug #7213: Use tab to ident in debian/rules or else it failsReleasedMatthieu CERDA2015-09-21Actions

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #7849: rudder-upgrade does not make some check on remote sql in case of distributed setupReleasedBenoît PECCATTE2016-01-27Actions
Actions
Copy link
 #1

Updated by Nicolas CHARLES about 9 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to Matthieu CERDA
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/743
Actions
Copy link
 #2

Updated by Nicolas CHARLES about 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #3

Updated by Matthieu CERDA about 9 years ago

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 9 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.

Actions
Copy link
 #5

Updated by Nicolas CHARLES almost 9 years ago

  • Related to Bug #7849: rudder-upgrade does not make some check on remote sql in case of distributed setup added
Actions
Copy link

Also available in: Atom PDF