Project

General

Profile

Actions
Copy link

Bug #7855

closed

When using a ${rudder.node.hostname} value in a component, the compliance level is always Unexpected

Added by Nicolas CHARLES almost 9 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
1 (highest)
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
3.1.19
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
45
Name check:
Fix check:
Regression:

Description

I used ${rudder.node.hostname} in a directive, for a component, and I always got unexepected status, even if the report has the right value (name of the node), and there is only one
I supposed it is linked to #7758

Switching to ${sys.fqhost} (which returns the same value) solved the issue

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #7758: When several directives value have a CFEngine var, we get "unexpected" due to bad regex matchingReleasedNicolas CHARLES2016-01-13Actions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 9 years ago

  • Related to Bug #7758: When several directives value have a CFEngine var, we get "unexpected" due to bad regex matching added
Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 9 years ago

Ok, could not reproduce :(

Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 9 years ago

but the expected report and the ruddersysevent table do match correctly, so there is no reason the the unknown

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.14 to 3.0.15
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.15 to 3.0.16
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.16 to 3.0.17
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.17 to 2.11.23
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.23 to 302
Actions
Copy link
 #9

Updated by Alexis Mousset over 8 years ago

  • Target version changed from 302 to 3.1.12
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #17

Updated by Jonathan CLARKE over 7 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques
Actions
Copy link
 #18

Updated by Benoît PECCATTE over 7 years ago

  • Priority set to 45
Actions
Copy link
 #19

Updated by Nicolas CHARLES over 7 years ago

  • Status changed from New to Rejected

Cannot reproduce, closing

Actions
Copy link

Also available in: Atom PDF