Bug #16553
closed
After first relay configuration, allowed networks are not taken into account
Added by Alexis Mousset almost 5 years ago.
Updated over 4 years ago.
Category:
System techniques
Description
What happens is that another apache conf edit exists in distributePolicy, so when server-roles tries to do it, it is skipped by the agent so apache does not use correct allowed networks settings.
- Has duplicate Bug #16547: Missing httpd restart on relay after webdav password update added
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Server Roles is always after Distribute Policy so we an move the restart & reports there
If there is a DistributePolicy, there is a Server Roles
- 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/1579
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
I tested that just after the relay gets its relay policies for the first time, if:
- a node is in relay allowed networks, then `rudder agent inventory` succeeds,
- a node is NOT in realy allowed networks, then `rudder agent inventory` fails.
So it seems to be ok.
- Name check changed from To do to Reviewed
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.3 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by