Project

General

Custom queries

Profile

Actions
Copy link

Bug #11636

closed

100% compliance on a disconnected node after changing the protocol

Added by Nicolas CHARLES over 7 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
6.1.19
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

Capture du 2017-10-19 22-43-19.png (81.6 KB) Capture du 2017-10-19 22-43-19.png Nicolas CHARLES, 2017-10-19 22:44
Actions
Copy link
 #1

Updated by Nicolas CHARLES over 7 years ago

table nodecompliance does not show compliance for the current time

Actions
Copy link
 #37

Updated by François ARMAND over 3 years ago

  • Status changed from New to Rejected

This setting does not exists anymore since several versions => closing that ticket.

Actions
Copy link

Also available in: Atom PDF