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 over 2 years ago.
Updated over 2 years ago.
Category:
System techniques
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
First impressions of Rudder
Effort required:
Very Small
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
- 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
i confirm that when the node as been promoted to relay, relayd is restarted, but no cf-serverd
it seems that in 6.x, the agent reloaded itself, but now in 7.x it doesn't anymore
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
- Target version changed from 7.1.0 to 7.1.1
- Target version changed from 7.1.1 to 7.0.3
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- 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
- Status changed from Pending technical review to Pending release
- 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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by