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 over 4 years ago. Updated 1 day ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
7.3.15
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
 #1

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.1 to 6.0.2
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.0.2 to 6.0.3
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.3 to 6.0.4
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.4 to 6.0.5
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.5 to 6.0.6
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.6 to 6.0.7
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.7 to 6.0.8
Actions
Copy link
 #8

Updated by François ARMAND almost 4 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 47

Setting that to "major" because it is not clear for an user why the page display "server can not be contacted".

Actions
Copy link
 #9

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.8 to 6.0.9
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.9 to 6.0.10
  • Priority changed from 47 to 45
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.10 to 798
  • Priority changed from 45 to 44
Actions
Copy link
 #12

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 798 to 6.1.14
  • Priority changed from 44 to 43
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
Copy link
 #21

Updated by Alexis Mousset 1 day ago

  • Target version changed from old 6.1 issues to relocate to 7.3.15
  • Priority changed from 43 to 0
Actions
Copy link

Also available in: Atom PDF