Actions
Bug #9401
closed
User story #1808: Add an Audit mode to Rudder: only check properties, no modification on nodes
Deleting a node should close its expected configuration
Status:
Released
Priority:
3
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When a node is deleted from rudder, we should close its expected configuration.
(in my case, I had deleted and reaccepted a node, and its promises weren't regenerated, which happened to be ok given the fact that its last node expected configuration was still open and valid)
Updated by François ARMAND about 8 years ago
- Status changed from New to In progress
Updated by François ARMAND about 8 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/1287
Updated by François ARMAND about 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|1bf3d6f780ba2eace330ddff498aa48b5ffaec66.
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 318 to 4.0.0~rc2
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 4.0.0~rc2 to 4.0.0~rc1
Updated by Alexis Mousset about 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.
Actions