Description of problem: man tuned-profiles-atomic-openshift-node speaks about "openshift-node-host" and "openshift-node-guest" instead the new ones (prefixed with atomic) Version-Release number of selected component (if applicable): 3.1 How reproducible: Install OSE 3.1 Steps to Reproduce: 1. man tuned-profiles-atomic-openshift-node 2. look for "atomic-openshift" Actual results: Nothing found Expected results: The real tuned profiles are shown Additional info:
https://github.com/openshift/origin/pull/6166
AOS rpms should now produce man pages that reference 'atomic-openshift-node-host' and 'atomic-openshift-node-guest' profiles.
Verified this bug with tuned-profiles-atomic-openshift-node-3.1.1.0-1.git.0.8632732.el7aos.x86_64, and PASS. # rpm -ql tuned-profiles-atomic-openshift-node /usr/lib/tuned/atomic-openshift-node-guest /usr/lib/tuned/atomic-openshift-node-guest/tuned.conf /usr/lib/tuned/atomic-openshift-node-host /usr/lib/tuned/atomic-openshift-node-host/tuned.conf /usr/share/licenses/tuned-profiles-atomic-openshift-node-3.1.1.0 /usr/share/licenses/tuned-profiles-atomic-openshift-node-3.1.1.0/LICENSE /usr/share/man/man7/tuned-profiles-atomic-openshift-node.7.gz # man tuned-profiles-atomic-openshift-node <--snip--> NAME tuned-profiles-atomic-openshift-node - description of profiles provided for OpenShift DESCRIPTION These profiles are provided for OpenShift nodes. They provide performance optimizations for OpenShift Nodes running on either bare metal (atomic-openshift-node-host) or virtual machines (atomic-openshift-node-guest). PROFILES The following profiles are provided: atomic-openshift-node-host Profile optimized for OpenShift hosts (bare metal). It is based on throughput-performance profile. It additionally increases SELinux AVC cache, PID limit and tunes netfilter connections tracking. atomic-openshift-node-guest Profile optimized for virtual OpenShift guests. It is based on virtual-guest profile. It additionally increases SELinux AVC cache, PID limit and tunes netfilter connections tracking. <--snip-->
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. https://access.redhat.com/errata/RHSA-2016:0070