Actions
Bug #20104
closed
No reporting on a fresh 7.0~beta2 install
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
In a fresh centos8 7.0~beta2, I can not get any reporting to work.
My webapp logs are filled with the following error:
[2021-10-11 13:48:32+0000] ERROR report - Could not get reports from the database, cause is: Could not get Reports with lowest id from the RudderSysEvents table <- Error running doobie transaction. Cause was: PSQLException: Bad value for type int : start
but I can not find any sysevent with such id when running:
psql -U rudder -h localhost -c "select id from ruddersysevents;"
Updated by François ARMAND about 3 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/3927
Updated by François ARMAND about 3 years ago
- Related to Architecture #20081: Add revision to rule added
Updated by François ARMAND about 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|f51d2a2bef6558584b9ee0baf90e42c2be5f5c04.
Updated by Vincent MEMBRÉ about 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.0~beta2 which was released today.
Actions