Project

General

Profile

Actions

Bug #17574

open

Trigger remote run leads to JS error in console and prevent displaying node properties

Added by Nicolas CHARLES almost 4 years ago. Updated about 1 month ago.

Status:
New
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
70
Name check:
To do
Fix check:
To do
Regression:
No

Description

When we trigger a remote run, when we get the node answer we also have a JS error in the console:

XML Parsing Error: syntax error
Location: https://192.168.43.2/rudder/secure/api/nodes/af8bc37f-56bd-4d40-866e-8bd25936f15d/applyPolicy
Line Number 1, Column 1:

It does still allows to show the agent run, but it prevents from displaying node properties values afterward
Properties can work again with reloading page.

Still happens in 7.2.6.


Files

clipboard-202011092213-blbro.png (69.6 KB) clipboard-202011092213-blbro.png François ARMAND, 2023-05-11 15:35

Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #18541: Trigger agent run lead to JS errorRejectedActions
Actions #1

Updated by Nicolas CHARLES almost 4 years ago

  • Subject changed from erreur when tiggering remote run to error when triggering remote run tht prevents displaying the node properties value
Actions #2

Updated by Nicolas CHARLES almost 4 years ago

response is described to be XML, but actual return is

Start execution with config [20200529-111953-454978fd]

Hostname        M| State         Technique                 Component                 Key                Message
192.168.43.5    E| compliant     Common                    ncf Initialization                           Configuration library initialization was correct
192.168.43.5    E| compliant     Common                    Update                                       Policy and configuration library are already up to date. No action required.
192.168.43.5    E| compliant     Common                    Security parameters                          The internal environment security is acceptable
192.168.43.5    E| compliant     Common                    CRON Daemon                                  Cron daemon status was correct
192.168.43.5    E| compliant     Common                    Log system for reports                       Logging system for report centralization is already correctly configured
192.168.43.5    E| compliant     Inventory                 inventory                                    Next inventory scheduled between 00:00 and 06:00
192.168.43.5    E| compliant     MOTD                      MOTD Configuration                           The MOTD file was correct
192.168.43.5    E| compliant     sshKeyDistribution        SSH key                   nch                SSH key "nch" for user nicolas was correct
192.168.43.5    E| repaired      tech_tech_technique       Command execution         /bin/true          Execute the command /bin/true was repaired
192.168.43.5    E| compliant     tech_tech_technique       File content              /tmp/foo           Insert

Actions #3

Updated by Nicolas CHARLES almost 4 years ago

  • Description updated (diff)
Actions #4

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.7 to 6.0.8
Actions #5

Updated by François ARMAND almost 4 years ago

  • Assignee set to Elaad FURREEDAN
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Effort required set to Small
  • Priority changed from 0 to 66
Actions #6

Updated by François ARMAND almost 4 years ago

Error messages appear in js console.

Actions #7

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.8 to 6.0.9
  • Priority changed from 66 to 65
Actions #8

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.9 to 6.0.10
  • Priority changed from 65 to 63
Actions #9

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.10 to 798
  • Priority changed from 63 to 62
Actions #10

Updated by Nicolas CHARLES over 3 years ago

  • Related to Bug #18541: Trigger agent run lead to JS error added
Actions #11

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 798 to 6.1.14
  • Priority changed from 62 to 55
Actions #12

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #13

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #14

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #16

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #17

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #18

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #19

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #20

Updated by François ARMAND 12 months ago

  • Related to deleted (Bug #18541: Trigger agent run lead to JS error)
Actions #21

Updated by François ARMAND 12 months ago

  • Has duplicate Bug #18541: Trigger agent run lead to JS error added
Actions #22

Updated by François ARMAND 12 months ago

  • Subject changed from error when triggering remote run tht prevents displaying the node properties value to Error in JS console when triggering remote run then prevents displaying the node properties value
  • Description updated (diff)
  • Assignee changed from Elaad FURREEDAN to Raphael GAUTHIER
  • Target version changed from old 6.1 issues to relocate to 7.2.7
  • UX impact set to It bothers me each time
  • Priority changed from 55 to 65
  • Regression set to No
Actions #23

Updated by François ARMAND 12 months ago

  • Subject changed from Error in JS console when triggering remote run then prevents displaying the node properties value to Trigger remote run leads to JS error in console and prevent displaying node properties
Actions #24

Updated by François ARMAND 12 months ago

  • Description updated (diff)
Actions #26

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 7.2.7 to 7.2.8
Actions #27

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.2.8 to 7.2.9
  • Priority changed from 65 to 66
Actions #28

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 7.2.9 to 7.2.10
Actions #29

Updated by Alexis Mousset 9 months ago

  • Target version changed from 7.2.10 to 7.2.11
  • Priority changed from 66 to 67
Actions #30

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 7.2.11 to 1046
Actions #31

Updated by Alexis Mousset 6 months ago

  • Target version changed from 1046 to 7.3.8
  • Priority changed from 67 to 68
Actions #32

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.8 to 7.3.9
Actions #33

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.9 to 7.3.10
Actions #34

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 7.3.10 to 7.3.11
  • Priority changed from 68 to 69
Actions #35

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 7.3.11 to 7.3.12
  • Priority changed from 69 to 70
Actions #36

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 7.3.12 to 7.3.13
Actions #37

Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 7.3.13 to 7.3.14
Actions

Also available in: Atom PDF