Project

General

Profile

Actions
Copy link

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

Status:
Released
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
System integration
Target version:
3.0.9
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

while merging #7154 from branch 2.11 to 3.0, a typo occured

Subtasks 1 (0 open — 1 closed)

Bug #7165: Typo in migration script, <<<<<<<<<<< HEAD remaining after a mergeReleasedMatthieu CERDA2015-09-04Actions
Actions
Copy link
 #1

Updated by Nicolas CHARLES over 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
Actions
Copy link
 #2

Updated by Nicolas CHARLES over 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
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 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)
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 9 years ago

  • Parent task set to #7154
Actions
Copy link
 #5

Updated by Nicolas CHARLES over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #7

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.

Actions
Copy link

Also available in: Atom PDF