Project

General

Profile

Actions
Copy link

Bug #17617

closed

After upgrading a node to relay, its allowed networks are incorrect

Added by Félix DALLIDET over 4 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
N/A
Assignee:
Elaad FURREEDAN
Category:
System techniques
Target version:
old 6.2 issues to relocate
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

I upgraded a node a to relay in a 6.1-nightly installation, and its allowed networks were not correct.
A restart of relayd fixed the issue, most likely because it restarted rudder-cf-serverd.

The restart should be done automatically when the configuration change

Actions
Copy link
 #1

Updated by Félix DALLIDET over 4 years ago

Ok restarting relayd does not restart cf-serverd, it is something else that fixed the allowed network. But I do not know what

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~rc3 to 6.1.0~rc4
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0~rc4 to 6.1.0
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.0 to 6.1.1
Actions
Copy link
 #5

Updated by François ARMAND over 4 years ago

  • Assignee set to Elaad FURREEDAN
Actions
Copy link
 #7

Updated by Elaad FURREEDAN over 4 years ago

  • Status changed from New to In progress
Actions
Copy link
 #8

Updated by Elaad FURREEDAN over 4 years ago

By default the promoted node collect allowed network from policy server, it shouldn't be the default since it is only the user who knows this information.
Ideas :
- Let the allowed network empty
- Be able to specify allowed network through the API
- Add an option that specifies to retriev allowed network from policy server (when he was a node)

Actions
Copy link
 #9

Updated by Elaad FURREEDAN over 4 years ago

  • Status changed from In progress to New
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.1 to 6.1.2
Actions
Copy link
 #11

Updated by François ARMAND over 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 32

I think what Felix talks about is not the fact that the relay gets allowed network from root server (for which you propositions make total sense), but I understand that the configured allowed networks weren't the ones actually applied to relay config.

Can you confirm Felix?

Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.2 to 6.1.3
Actions
Copy link
 #13

Updated by François ARMAND over 4 years ago

  • Target version changed from 6.1.3 to 6.1.4
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 6.1.4 to 6.1.5
  • Priority changed from 32 to 31
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.5 to 6.1.6
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.6 to 6.1.7
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.7 to 6.1.8
  • Priority changed from 31 to 30
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.8 to 6.1.9
  • Priority changed from 30 to 29
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.9 to 6.1.10
Actions
Copy link
 #20

Updated by Alexis Mousset almost 4 years ago

  • Category changed from Relay server or API to System techniques
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.10 to 6.1.11
  • Priority changed from 29 to 28
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.11 to 6.1.12
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.12 to 6.1.13
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.13 to 6.1.14
  • Priority changed from 28 to 27
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Vincent MEMBRÉ about 3 years ago

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

Updated by Vincent MEMBRÉ about 3 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Alexis Mousset almost 2 years ago

  • Target version changed from old 6.1 issues to relocate to old 6.2 issues to relocate
  • Priority changed from 27 to 0
Actions
Copy link
 #34

Updated by Alexis Mousset over 1 year ago

  • Regression set to No

we have fixed cf-serverd restart

Actions
Copy link
 #35

Updated by Alexis Mousset over 1 year ago

  • Status changed from New to Rejected
Actions
Copy link

Also available in: Atom PDF