Jiri do you need /etc/tuned/bootcmdline for anything? Because if not I would propose more flexible approach allowing global disablement of the plugins through the tuned-main.conf, e.g.:
plugins_disabled = bootloader

This would globally disable any usage of the bootloader plugin in the TuneD profiles with INFO message that the plugin is disabled.

Moreover this approach would allow global disabling of any combination of plugins, e.g.
plugins_disabled = bootloader, scheduler

Thank you for lookingn into this, Jardo!

(In reply to Jaroslav Škarvada from comment #2)
> Jiri do you need /etc/tuned/bootcmdline for anything? Because if not I would
> propose more flexible approach allowing global disablement of the plugins
> through the tuned-main.conf, e.g.:
> plugins_disabled = bootloader

Yes, we do need and use /etc/tuned/bootcmdline file in RHOCP.  What we do
at the moment is run TuneD in a container which discards all the modifications TuneD does
to the host filesystem (there are some exceptions though).  However, we do use
/etc/tuned/bootcmdline file to to gather the calculated kernel parameters.  That
information is then fed as configuration to another RHOCP operator (MCO) which
then adjusts the kernel parameters and reboots the host machine.

The reasoning behind this request is that the plan is to run TuneD outside of the 
container directly on the host and we need to disable any conflicting changes on the host
filesystem TuneD does while keeping the useful stuff such as calculating the kernel
boot parameters in its own directory (/etc/tuned).