Actions
Bug #6518
closed
When we regenerate promises via 'Update' button, all promises are regenerated even if not needed
Status:
Released
Priority:
2
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If I click on update now, Rudder will regenerate all promises, on all nodes.
Same, if I change a directive, rule or group, it will regenerate averything, even if there is no need for it
The problem is on the coparision between the cache and the generated hash: it checks also for the written date, that does not exists in the generated hash. So Rudder thinks all the nodes have changed
Updated by Nicolas CHARLES over 9 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/849
Updated by Nicolas CHARLES over 9 years ago
This also greatly improves the perfs of each deployment !
Updated by Nicolas CHARLES over 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|861541a834b16d6b7510a94e2fc3d2dbe2d611c6.
Updated by François ARMAND over 9 years ago
Applied in changeset rudder|b5311a24c98ddfe1084700c4c4f09fc6cb42c3fd.
Updated by Vincent MEMBRÉ over 9 years ago
- Subject changed from When we click on "update now", all promises are always regenerated - and same when changing any configuration parameter to When we regenerate promises via 'Update' button, all promises are regenerated even if not needed
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.11 and 3.0.5 which were released today.
- Announcement 2.11
- Changelog 2.11 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions