Actions
Bug #6206
closedOn policy server, we do override the run interval, and the expected frequency for reports, but the generated promises don't override the heartbeat frequency, causing non answer in the webapp
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Rudder component run every 5 minutes, and their reports are expected every 5 minutes
However, we do not overrride the heartbeat frequency in the generated promises, causing no answer in the web interface
Updated by Nicolas CHARLES almost 10 years ago
- Status changed from New to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/807
Updated by Nicolas CHARLES almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset b720e5e222dd725f8e0b7217d171d310c54f32e0.
Updated by François ARMAND almost 10 years ago
Applied in changeset 9c8a951ae4377224be6c70f5fc61558c676a47de.
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0, which was released on 2015/02/16
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions