I believe this is fixed in master, is it not?
Running testing with openshift-ansible-3.10.0-0.22.0, but failed. # cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.5 (Maipo) # rpm -q kernel kernel-3.10.0-862.el7.x86_64 # rpm -q tuned tuned-2.9.0-1.el7.noarch # rpm -qa|grep openshift|grep tune <empty> No openshift tune rpm is installed now. installer is installing tune profile into /etc/tuned/{openshift,openshift-control-plane,openshift-node}/ # ls /etc/tuned active_profile bootcmdline openshift openshift-control-plane openshift-node profile_mode recommend.conf recommend.d tuned-main.conf On master: # tuned-adm recommend openshift-control-plane # tuned-adm list Available profiles: - balanced - General non-specialized tuned profile - desktop - Optimize for the desktop use-case - latency-performance - Optimize for deterministic performance at the cost of increased power consumption - network-latency - Optimize for deterministic performance at the cost of increased power consumption, focused on low latency network performance - network-throughput - Optimize for streaming network throughput, generally only necessary on older CPUs or 40G+ networks - openshift - Optimize systems running OpenShift (parent profile) - openshift-control-plane - Optimize systems running OpenShift control plane - openshift-node - Optimize systems running OpenShift nodes - powersave - Optimize for low power consumption - throughput-performance - Broadly applicable tuning that provides excellent performance across a variety of common server workloads - virtual-guest - Optimize for running inside a virtual guest - virtual-host - Optimize for running KVM guests Current active profile: openshift-control-plane This is correct. on node: # tuned-adm list Available profiles: - balanced - General non-specialized tuned profile - desktop - Optimize for the desktop use-case - latency-performance - Optimize for deterministic performance at the cost of increased power consumption - network-latency - Optimize for deterministic performance at the cost of increased power consumption, focused on low latency network performance - network-throughput - Optimize for streaming network throughput, generally only necessary on older CPUs or 40G+ networks - openshift - Optimize systems running OpenShift (parent profile) - openshift-control-plane - Optimize systems running OpenShift control plane - openshift-node - Optimize systems running OpenShift nodes - powersave - Optimize for low power consumption - throughput-performance - Broadly applicable tuning that provides excellent performance across a variety of common server workloads - virtual-guest - Optimize for running inside a virtual guest - virtual-host - Optimize for running KVM guests Current active profile: openshift-node But the following command return: # tuned-adm recommend openshift-control-plane Which should be some "openshift-node".
This was already fixed for 3.9. In 3.10, the content of /etc/origin/node/node-config.yaml changed and cannot be used during the installation as it is now. See: https://bugzilla.redhat.com/show_bug.cgi?id=1569917