Rudder

I think you're right and maybe only the agent should be disabled on root server ? (and also relay ??)

@Team, Would it be possible ?? what do you think of it ?

Thank you for reporting this, there is indeed a problem with current agent and cf-serverd's service behaviour.

Current situation¶

• The rudder-agent service starts two daemons:
  • cf-serverd wich:
    • allows trigerring a remote-run on all nodes
    • serves policy files from relays and root servers (which is definitely a server feature)
  • cf-execd which regularly triggers an agent run
• disabling the agent also prevents both agent services (cf-execd and cf-serverd) from starting
• there is an option is disable command to also stop the agent service

Problems:

• Keeping a service running but preventing it from restarting makes not sense.
• It is unexpected that acting on the agent would break policy server, and worse that it is not possible to keep it working with a disabled agent.
• There is a clash between cf-serverd usages between simple nodes and servers. It is part of agent (package, service, etc). but also acts as a server component.

Short term changes¶

• Make cf-serverd (and cf-execd for consistency) ignore agent state:
  • change policies to ignore disable flag
  • change systemd unit to ignore disable flag
• rudder agent stop or rudder agent disable -s will still stop cf-execd and cf-serverd

Long term changes¶

This would requires wider changes to Rudder.

We could run two separate cf-serverd daemons, one for remote-run and one as policy-server, probably on different ports. This would allow better service organization and avoid unexpected behaviour.

What do you think about this solution?

The short term version is small

PR https://github.com/Normation/rudder-packages/pull/2146

Applied in changeset rudder-packages|4ee1137ef4eb945490fb4589b24f39b671118f92.

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

• 6.0.0 changelog
• Upgrade manual