Bug #9333
closed
User story #1808: Add an Audit mode to Rudder: only check properties, no modification on nodes
Bug #9303: Policy Mode is not used to know if a node configuration changed
If we change the global policy mode, promises are not generated if we click on "update policies"
Description
I switched from "Audit" to "Enforce" policy mode in the settings page, and the promises were not regenerated. Clicking on "Update policies" did not trigger a promise generation
Changing on the directive level trigger a correct generation thought
Updated by François ARMAND about 8 years ago
It should be on the cache, right.
And on the same level, compliance mode should be in the cache, to, because since 4.0, it goes in nodeConfigurations expected reports.
And agent run should go in cache, to.
Updated by François ARMAND about 8 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
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/1283
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|16b718d88fc46f8c5a7470fd64048f33ae50e57d.
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.