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 almost 10 years ago.
Updated almost 10 years ago.
Description
In parent ticket, we changed the database schema
This ticket is to create the migration script
- 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
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- 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.
- Related to Bug #7849: rudder-upgrade does not make some check on remote sql in case of distributed setup added
Also available in: Atom
PDF