Werk #19460: Synthetic Monitoring: Root agent deployment on Linux is no longer supported in combination with RCC as environment creation mode
| Component | Checks & agents | ||||
| Title | Synthetic Monitoring: Root agent deployment on Linux is no longer supported in combination with RCC as environment creation mode | ||||
| Date | May 3, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Incompatible - Manual interaction might be required | ||||
| Checkmk versions & editions |
|
When RCC (used by Synthetic Monitoring) runs as root on Linux and the RCC home
directory (e.g. /opt/robocorp) does not yet exist, RCC may change the
permissions of /opt from 555 (the default on SLES 16) to 750. This breaks all workflows where
non-root users need to traverse /opt, including Checkmk sites installed under
/opt/omd — as observed on SLES 16.
Baking a Linux agent package that combines root agent deployment with at least one RCC-based plan now fails with a clear error message instead of producing a broken package.
Migration: Either switch the affected hosts to non-root agent deployment via the rule Customize agent package (Linux), or replace the RCC environment with a Conda environment for the affected plans.