Description of problem:

We had a problem recently where a wrong configuration of the NFV profile caused the profile not be loaded during boot (reproducer sequence below). The only place where I could find an indication of the error was in tuned logs. There's nothing in systemd:

[root@rhel73-single ~]# systemctl status tuned
● tuned.service - Dynamic System Tuning Daemon
   Loaded: loaded (/usr/lib/systemd/system/tuned.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2016-10-17 14:49:38 EDT; 29s ago
 Main PID: 1066 (tuned)
   CGroup: /system.slice/tuned.service
           └─1066 /usr/bin/python -Es /usr/sbin/tuned -l -P

Oct 17 14:49:37 rhel73-single systemd[1]: Starting Dynamic System Tuning Daemon...
Oct 17 14:49:38 rhel73-single systemd[1]: Started Dynamic System Tuning Daemon.
[root@rhel73-single ~]# 

So it feels like tuned is reporting success to systemd, even though it failed to load properly.

NOTE: I suspect this issue has always existed.

Version-Release number of selected component (if applicable): tuned-2.7.1-4.el7fdb.noarch


How reproducible:


Steps to Reproduce:
1. Make a mistake to tuned profile configuration. For example, in the case of the NFV profile, write the following to /etc/tuned/realtime-variables.conf for a guest with only 2 vCPUs:

isolated_cores=1,3

2. Boot the guest
3. Check the load of the profile has failed during boot:

[root@rhel73-single ~]# tuned-adm active
No current active profile.
[root@rhel73-single ~]# 

4. Check systemd status as indicated above