Actions
Architecture #25087
closed
Architecture #24963: Persist compliance in base to know last state for a long time
Remove unexpected interpretation choice for vars because it's not meaningful anymore
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Fix check:
To do
Regression:
No
Description
Since #20540 we removed the last alternative for unexpected interpretation, and since Rudder Bug #12719: Some reports are duplicated between agent and postgres leading to "unexpected" compliance (rudder 4.1, so forever), the default value is "don't care", and I don't think anybody would change it. It would breaks iterators, blocks, etc.
So we need to just remove it completly.
Updated by François ARMAND 5 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 5 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/5754
Updated by Anonymous 5 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|ebbfdf200e0240cd923ca236e8a56ca6328ffb30.
Updated by Anonymous 5 months ago
Applied in changeset rudder|34d51149b061565424f1b69b1a8ce0fdefef66bb.
Updated by Alexis Mousset 4 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.0~alpha1 which was released today.
Actions