Actions
Bug #11636
closed
100% compliance on a disconnected node after changing the protocol
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
On Rudder 4.2, I changed the setting to use DNS configuration, policy were generated, and was surprised to see that a powered-off relay reported 100% compliance (see screenshot)
Happen on 4.2, but surely also on 4.1
I guess there's an issue in the computation of expiration of compliance when node is not answering, and policy were generated
Files
Updated by
Updated by Benoît PECCATTE over 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 32
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.10 to 4.1.11
- Priority changed from 32 to 31
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.11 to 4.1.12
- Priority changed from 31 to 30
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.12 to 4.1.13
- Priority changed from 30 to 29
Updated by Benoît PECCATTE over 6 years ago
- Target version changed from 4.1.14 to 4.1.15
- Priority changed from 29 to 28
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.15 to 4.1.16
- Priority changed from 28 to 27
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 27 to 0
Updated by 
Updated by 
Actions