Actions
Bug #11037
closedMissing agent reports after Rudder server restart
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Rudder 4.1.3
After doing restart ("service rudder-jetty restart"), last reports received before restart looks to be missed.
All listed nodes are shown in "No report"|"Missing reports" state until new report will be processed.
Expect to store|retrieve the last versions from db.
Updated by François ARMAND over 7 years ago
- Related to Bug #10881: Almost nodes become in "red state" after upgrading from 4.0.2 to 4.1.3 added
Updated by François ARMAND over 7 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Priority changed from 0 to 70
Updated by Nicolas CHARLES over 7 years ago
I had a similar one, when after restart, I got a random id identified as last run (which was wrong)
Updated by Alexis Mousset over 7 years ago
- Subject changed from Missing agent reports after Ruder server restart to Missing agent reports after Rudder server restart
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 4.1.6 to 4.1.7
Updated by François ARMAND over 7 years ago
- Translation missing: en.field_tag_list set to Sponsored
- Priority changed from 69 to 93
We have now several users who reported that, and even if not really "critical", it is scary and extremelly visible.
Updated by François ARMAND over 7 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES over 7 years ago
- Related to Bug #10456: Several core features don't work anymore with more than 1000 nodes added
Updated by Nicolas CHARLES over 7 years ago
- Assignee changed from François ARMAND to Nicolas CHARLES
Updated by François ARMAND over 7 years ago
- Related to deleted (Bug #10881: Almost nodes become in "red state" after upgrading from 4.0.2 to 4.1.3)
Updated by François ARMAND over 7 years ago
- Has duplicate Bug #10881: Almost nodes become in "red state" after upgrading from 4.0.2 to 4.1.3 added
Updated by Nicolas CHARLES over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1730
Updated by Nicolas CHARLES over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|18e2e96dea6987db199bd47f4b2ea8f912e43b64.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.7 and 4.2.0~rc1 which were released today.
- 4.1.7: Announce Changelog
- 4.2.0~rc1: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions