Project

General

Profile

Actions

Bug #16668

closed

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

Added by Florian Heigl over 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Server components
Target version:
-
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
15
Name check:
To do
Fix check:
To do
Regression:

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.

Actions #1

Updated by Alexis Mousset over 4 years ago

Was it with syslog or HTTP reporting?

Actions #2

Updated by Alexis Mousset over 4 years ago

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

Actions #3

Updated by François ARMAND over 4 years 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.

Actions #4

Updated by François ARMAND over 4 years 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
Actions #5

Updated by François ARMAND almost 3 years ago

  • Status changed from New to Resolved
  • Priority changed from 17 to 15

We enhanced a lot remote run since then, and now output are quite consistant.

Actions

Also available in: Atom PDF