Project

General

Profile

Actions
Copy link

Bug #5316

closed

If policy server hostname changes, the generated promises never take into account the new value

Added by Nicolas CHARLES over 10 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
3.1.19
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

We use the variable POLICYSERVER to define in the promises, what is the hostname of the policy server of a node
However, this value is defined at creation, by the user, and it is never updated. So it can never be updated automatically

I wonder if we should not directly use ${rudder.node.policyserver.hostname}

Related issues 3 (0 open — 3 closed)

Related to Rudder - Bug #1411: Node (hostname,policyserver,...) modification should trigger promises regenerationReleasedNicolas CHARLESActions
Related to Rudder - Bug #8046: Change of Policy Server does not trigger a PolicyupdateRejectedFrançois ARMAND2016-03-08Actions
Related to Rudder - User story #8247: Changing hostname or policy server of one node force regeneration of all rules on the nodeRejectedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.10.4 to 2.6.18
Actions
Copy link
 #2

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.18 to 2.10.5
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.10.5 to 2.10.6
Actions
Copy link
 #4

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 2.10.6 to 2.10.7
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.10.7 to 2.10.8
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.10.8 to 2.10.9
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions
Copy link
 #12

Updated by Benoît PECCATTE over 9 years ago

  • Category set to System techniques
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.20 to 277
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 277 to 2.11.18
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions
Copy link
 #24

Updated by François ARMAND over 8 years ago

  • Related to Bug #1411: Node (hostname,policyserver,...) modification should trigger promises regeneration added
Actions
Copy link
 #25

Updated by François ARMAND over 8 years ago

  • Related to Bug #8046: Change of Policy Server does not trigger a Policyupdate added
Actions
Copy link
 #26

Updated by François ARMAND over 8 years ago

  • Related to User story #8247: Changing hostname or policy server of one node force regeneration of all rules on the node added
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ about 8 years ago

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

Updated by Vincent MEMBRÉ about 8 years ago

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

Updated by Vincent MEMBRÉ about 8 years ago

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

Updated by Vincent MEMBRÉ about 8 years ago

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

Updated by Vincent MEMBRÉ almost 8 years ago

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

Updated by François ARMAND over 7 years ago

  • Status changed from New to Rejected
  • Priority set to 0

This variable is not used anymore.

Actions
Copy link

Also available in: Atom PDF