Actions
Bug #7161
closedBug #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
Pull Request:
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
Updated by Nicolas CHARLES over 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
Updated by Nicolas CHARLES over 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-packages|50e46d6eb0c94a2e37b1d6e4f42c659592f82279.
Updated by Matthieu CERDA over 9 years ago
Applied in changeset rudder-packages|c1f24f5fc1fc0f6e813e40fd53f79ed04d6449cc.
Updated by Vincent MEMBRÉ about 9 years ago
- Status changed from Pending release to Released
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