Bug 1677649

Description of problem:
When changing the CPU affinity of IRQs using the 'isolated_cores' facility of the 'scheduler' plugin, no errors are reported during profile activation, if changing the affinity is not supported.

In contrast, during verification of the tuning, for IRQs that do not support changing the CPU affinity, errors are reported if the CPU affinity different than expected.

This is inconsistent. We should not print the errors during verification. Debug messages should be logged instead, which is what we do during profile activation.

Version-Release number of selected component (if applicable):
tuned-2.10.0-14.el8.noarch

How reproducible:
always on systems that have IRQs that don't support changing their CPU affinity

Steps to Reproduce:
# cat /etc/tuned/test/tuned.conf
[scheduler]
isolated_cores=1
# systemctl stop tuned
# > /var/log/tuned/tuned.log
# tuned-adm profile test
# grep ERROR /var/log/tuned/tuned.log
# > /var/log/tuned/tuned.log
# tuned-adm verify
# grep ERROR /var/log/tuned/tuned.log

Actual results:
When tuned.log is checked the first time, there are no errors. When the log is checked the second time, there are errors:
2019-02-15 08:19:32,664 ERROR    tuned.plugins.plugin_scheduler: verify: failed: 'SMP affinity of IRQ 0' = '[0, 1]', expected '[0]'
2019-02-15 08:19:32,664 ERROR    tuned.plugins.plugin_scheduler: verify: failed: 'SMP affinity of IRQ 24' = '[0, 1]', expected '[0]'
2019-02-15 08:19:32,664 ERROR    tuned.plugins.plugin_scheduler: verify: failed: 'SMP affinity of IRQ 25' = '[0, 1]', expected '[0]'

Expected results:
There are no errors in either case.