Rudder

Hello!

We use rudder to ensure some packages (either apt or yum) are installed on servers.

So regularly rudder launch apt-get update and yum update, thus locking the packages database, as expected.

But when we deploy configuration and/or software using deployment tools (in our case, ansible), we use the package manager to install packages, or check the installed version, but when rudder is running just at this moment, it crashes because of locking exclusivity. For example, `Failed to lock apt for exclusive operation`

As the rudder agent is by design hard to disable totally, I want to know if there is possibility to disable it temporarily, or tell him to do not some action (eg: dealing with package) during some time, something we could enable at the start of our deployment, to be sure rudder does not interfere.

As you may understand, crashing a deployment after sometimes 15 to 20min of play, because of such an error, and having to redeploy is frustrating for the team ^^"

Is something like that already possible, or have you an idea for a workaround?

Thanks!

Regards,

Victor Héry