Actions
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
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
System integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Updated by Nicolas CHARLES about 9 years ago
- Related to Bug #7154: Agent schedule is not historised, so we can't know what was the agent run interval in the past added
Updated by Nicolas CHARLES about 9 years ago
- 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
Updated by Vincent MEMBRÉ about 9 years ago
- Related to deleted (Bug #7154: Agent schedule is not historised, so we can't know what was the agent run interval in the past)
Updated by Nicolas CHARLES about 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|d5aa6c8baab2c34773516a67d42847e4d192aa61.
Updated by François ARMAND about 9 years ago
Applied in changeset rudder|49f1bf02d29ba54f7eae397bd8b6dd947209e60e.
Updated by Vincent MEMBRÉ about 9 years ago
- 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.
- 3.0: Announce Changelog
- 3.1: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions