Project

General

Profile

Actions
Copy link

Bug #20993

closed

When updating allowed networks of a relay, rudder-cf-serverd service does not seem to be restarted

Added by Félix DALLIDET about 2 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
System techniques
Target version:
7.0.3
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
108
Name check:
To do
Fix check:
To do
Regression:

Description

This is an issue as it delays the propagation of the allowed-network setting.
It was seen in 7.1 but the issue might be present in 7.0

Actions
Copy link
 #1

Updated by Félix DALLIDET about 2 years ago

  • Severity changed from Critical - prevents main use of Rudder | no workaround | data loss | security to Minor - inconvenience | misleading | easy workaround
  • Priority changed from 152 to 109
Actions
Copy link
 #2

Updated by Nicolas CHARLES about 2 years ago

i confirm that when the node as been promoted to relay, relayd is restarted, but no cf-serverd

Actions
Copy link
 #3

Updated by Nicolas CHARLES about 2 years ago

it seems that in 6.x, the agent reloaded itself, but now in 7.x it doesn't anymore

Actions
Copy link
 #4

Updated by Nicolas CHARLES about 2 years ago

running systemctl reload-or-restart rudder-cf-serverd workarounds the issue

It should be run automatically by the policies, when file /opt/rudder/etc/rudder-networks-24.conf is updated

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.1.0 to 7.1.1
Actions
Copy link
 #6

Updated by Nicolas CHARLES almost 2 years ago

  • Target version changed from 7.1.1 to 7.0.3
Actions
Copy link
 #7

Updated by Nicolas CHARLES almost 2 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions
Copy link
 #8

Updated by Nicolas CHARLES almost 2 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1763
Actions
Copy link
 #9

Updated by Nicolas CHARLES almost 2 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending release to Released
  • Priority changed from 109 to 108

This bug has been fixed in Rudder 7.0.3 which was released today.

Actions
Copy link

Also available in: Atom PDF