Actions
Bug #9517
closedOn a fresh Rudder 4.0 install, expectedreports and expectedreportsnodes table are still present
Status:
Released
Priority:
N/A
Assignee:
Category:
System integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
They are here, but empty:
rudder=> select * from expectedreports; rudder=> select * from expectedreportsnodes; nodejoinkey | nodeid | nodeconfigids | overriden -------------+--------+---------------+----------- (0 rows)
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 4.0.0~rc3 to 4.0.0~rc4
Updated by Vincent MEMBRÉ about 8 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1347
Updated by Vincent MEMBRÉ about 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|c5c71f4c065f84237e4ed4e0781ee6c20d776f02.
Updated by Alexis Mousset about 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.
Actions