Patch posted: https://github.com/redhat-openstack/astapor/pull/121 To test: Apply a compute node of any type When applying, you should see output similar to: Info: /Stage[main]/Quickstack::Tuned::Common/Service[tuned]: Scheduling refresh of Exec[tuned-virtual-host] Info: /Stage[main]/Quickstack::Tuned::Common/Service[tuned]: Unscheduling refresh on Service[tuned] Notice: /Stage[main]/Quickstack::Tuned::Virtual_host/Exec[tuned-virtual-host]/returns: executed successfully Notice: /Stage[main]/Quickstack::Tuned::Virtual_host/Exec[tuned-virtual-host]: Triggered 'refresh' from 1 events Look to see if tuned service is installed: service tuned status tuned (pid 2882) is running… See if the expected profile is running: # /usr/sbin/tuned-adm active | /bin/grep virtual-host Current active profile: virtual-host
Verified :(Havana A2 - RHOS4.0 2014-02-17.1) - openstack-foreman-installer-1.0.4-1.el6ost.noarch Tested On 2 Compute-nodes deployed **by foreman** ( 1 X neutron-compute-node / 1X nova-network-compute-node ): Test: ----- service tuned status tuned (pid 6746) is running... /usr/sbin/tuned-adm active | /bin/grep virtual-host Current active profile: virtual-host
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0213.html