Werk #19460 disallowed combining root agent deployment on Linux with RCC as environment creation mode, since RCC could otherwise break permissions on /opt (e.g. on SLES 16), affecting all workflows relying on non-root access to that directory.
Some customers rely on custom plugins or automations with hardcoded paths that assume a root agent context and cannot easily be adapted.
For these cases, the new option "Allow agent deployment as root" (available in the rule "Robotmk Scheduler (Linux)" under the RCC-related settings) bypasses this restriction.
This option is disabled by default. It should only be enabled if the affected host is not used for any other purpose and the implications of running RCC as root as explained in Werk #19460 are understood.
To the list of all Werks