Bug #7164
closed
Bug #7154: Agent schedule is not historised, so we can't know what was the agent run interval in the past
typo in the sql schema following a merge 2.11->3.0
Added by Nicolas CHARLES about 9 years ago.
Updated about 9 years ago.
Category:
System integration
Description
while merging #7154 from branch 2.11 to 3.0, a typo occured
- Related to Bug #7154: Agent schedule is not historised, so we can't know what was the agent run interval in the past added
- Status changed from New to Pending technical review
- Assignee set to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/923
- Related to deleted (Bug #7154: Agent schedule is not historised, so we can't know what was the agent run interval in the past)
- 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 3.0.9 and 3.1.2 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by