Actions
Bug #8337
closed
Broken compliance summary on a node
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
See attached screenshot, it seems there is an issue in the computation of global compliance for the node.
Files
Updated by Alexis Mousset over 8 years ago
I reloaded the page and another directive appeared as missing.
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.10 to 3.1.11
Updated by François ARMAND over 8 years ago
- Related to Bug #8051: Compliance is not correctly computed if we receive run agent right after generation added
Updated by François ARMAND over 8 years ago
We believe it could have been to #8051.
We are closing that one, but we are keeping an eye open to that problem in the future.
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.11 to 3.1.12
Updated by François ARMAND over 8 years ago
- Related to deleted (Bug #8051: Compliance is not correctly computed if we receive run agent right after generation)
Updated by François ARMAND over 8 years ago
- Is duplicate of Bug #8051: Compliance is not correctly computed if we receive run agent right after generation added
Actions