Bug #27180
Updated by François ARMAND 23 days ago
If we have node compliance that is configured for more than 3 days, and we reached the point where all ruddersysevents are cleaned, then: - we do have the log message "last node run is too old but compliance persistance is configured for that node for XXX days" - but the compliance bar in UI remains forever in stipped blue - and we have "never" in last seen column. So it seems that when we don't have any runs remaining in @ruddersysevent@, then we don't reach "is there compliance" in the UI, BUT we still have the log. In that case, the explain compliance logs show: <pre> 2025-07-01 17:25:00+0200 DEBUG explain_compliance.384c0785-0291-4964-9249-xxx - Run config for node 384c0785-0291-4964-9249-xxx: 384c0785-0291-4964-9249-5bf940599022: NoReportInInterval : no run (ever or too old) 2025-07-01 17:25:00+0200 DEBUG explain_compliance.384c0785-0291-4964-9249-xxx - Computing compliance for node 384c0785-0291-4964-9249-xxx 384c0785-0291-4964-9249-5bf940599022 with: [NoReportInInterval: expected NodeConfigId: 20250701-171458-df83b9fc/[20250701T171458+0200-now]| last run: none available (or too old)] 2025-07-01 17:25:00+0200 DEBUG explain_compliance.384c0785-0291-4964-9249-xxx - Node didn't received reports recently, status depend of the compliance mode and previous report status 2025-07-01 17:25:00+0200 INFO compliance - Node with id '384c0785-0291-4964-9249-xxx' hasn't send report in expected time but rudder.compliance_expiration_policy is configured to keep compliance for 93 days: waiting until 2025-10-02T17:35:00+02:00 </pre> !clipboard-202507011738-wpzgo.png!