Jenkins stores slave information as well as their status in the main config file. As we've automated the configuration via Puppet, any automated changes trigger and overwrite and service restart (if not handled properly). Such is the case for slave state changes, e.g. when a slave goes offline due to disk usage issues.

Suggestion: split of slave configuration (or at least their status information) into a separate configuration file.