Actions
Bug #5511
closed
Accepting Nodes via API does not trigger policy update
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Accepting nodes via API does not trigger automatic deployment
We shoud trigger one
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from New to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/605
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset e7ecc48371f29520ede0bb3e0054f27184da651b.
Updated by François ARMAND about 10 years ago
Applied in changeset c4fe8ea957981e34461899b2befdebc514528003.
Updated by Matthieu CERDA about 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000038.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog27
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Matthieu CERDA about 10 years ago
This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-October/000109.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions