Project

General

Profile

Bug #16668

Sometime, compliance is not consistant with remote run output before manual refresh

Added by Florian Heigl 6 months ago. Updated about 1 month ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Server components
Target version:
-
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
17

Description

Not sure if true, but looks like.
Two remote runs, no influence on compliance status in UI.

I need another agent run locally on the managed node, compliance updates.

#1

Updated by Alexis MOUSSET 4 months ago

Was it with syslog or HTTP reporting?

#2

Updated by Alexis MOUSSET 4 months ago

Output of remote run is not parsed, and reports follow the usual path it may take some (short) time.

#3

Updated by François ARMAND about 1 month ago

  • Priority changed from 18 to 17

I think that there is sometimes a lag (perhaps depending to load or whatever). I also felt that reports for remote run weren't applying immediately, which is disturbing (you see an error, or 100% success in run output, and not the same thing below in compliance bar), and you need to refresh compliance to get correct result.

It's hard to reproduce consistantly, though.

#4

Updated by François ARMAND about 1 month ago

  • Subject changed from logs from rudder remote run seem to bypass UI to Sometime, compliance is not consistant with remote run output before manual refresh

Also available in: Atom PDF