Project

General

Profile

Actions
Copy link

Bug #16442

open

Compliance page unaccessible when the node is set with set-force-audit

Added by Félix DALLIDET almost 5 years ago. Updated 5 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
7.3.17
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

If I force locally on a node to run only in audit mode (rudder agent set-force-audit) and I do not force this same node to run in audit via the interface, it aborts all its run.
This is as expected and works fine.

But when doing it, the aborted run are not interpreted by the webapp and I cannot access the compliance page of the node, I always end up with a popup displaying: "The server cannot be contacted at this time".

When I force the agent to run in audit mode, the runs are then normal and the compliance is correctly shown.

Actions
Copy link

Also available in: Atom PDF