Project

General

Profile

Actions

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

Status:
Released
Priority:
1
Assignee:
Matthieu CERDA
Category:
Packaging
Target version:
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 open1 closed)

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

Related issues 1 (0 open1 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 #1

Updated by Nicolas CHARLES over 8 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 #2

Updated by Nicolas CHARLES over 8 years ago

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

Updated by Matthieu CERDA over 8 years ago

Actions #4

Updated by Vincent MEMBRÉ over 8 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 #5

Updated by Nicolas CHARLES about 8 years ago

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

Also available in: Atom PDF