Project

General

Profile

Actions

Bug #5316

closed

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

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

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
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 open3 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 #1

Updated by Nicolas PERRON about 10 years ago

  • Target version changed from 2.10.4 to 2.6.18
Actions #2

Updated by Nicolas PERRON about 10 years ago

  • Target version changed from 2.6.18 to 2.10.5
Actions #3

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.10.5 to 2.10.6
Actions #4

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 2.10.6 to 2.10.7
Actions #5

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.7 to 2.10.8
Actions #6

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.8 to 2.10.9
Actions #7

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions #8

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions #9

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions #10

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions #11

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions #12

Updated by Benoît PECCATTE over 9 years ago

  • Category set to System techniques
Actions #13

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions #14

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions #15

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions #16

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions #17

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions #18

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions #19

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.20 to 277
Actions #20

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 277 to 2.11.18
Actions #21

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #22

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #23

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #24

Updated by François ARMAND over 8 years ago

  • Related to Bug #1411: Node (hostname,policyserver,...) modification should trigger promises regeneration added
Actions #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 #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 #27

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #28

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #29

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #30

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.24 to 308
Actions #31

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 308 to 3.1.14
Actions #32

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #33

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #34

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #35

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #36

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #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

Also available in: Atom PDF