Description of problem: When a cluster gets installed with 3.6 then upgrades 3.7 -> 3.8 -> 3.9+ The tuned profile rpm is no login available in 3.9+ and gets removed during the upgrade. The upgrade never runs role: tuned. The only plays that call this role are as follows. ./playbooks/openshift-loadbalancer/private/config.yml: - role: tuned ./playbooks/openshift-master/private/config.yml: - role: tuned ./playbooks/openshift-node/private/configure_nodes.yml: - role: tuned In 3.7+ fresh installs the tuned role will be run. Version-Release number of the following components: Upgrade playbooks 3.7+ How reproducible: 100% Steps to Reproduce: 1. Install 3.6 cluster and upgrade to at 3.9 2. Check output of `tuned-adm --list Actual results: # tuned-adm active Current active profile: virtual-guest Expected results: # tuned-adm active Current active profile: openshift-control-plane Additional info: The upgrade playbooks should always call the tuned role to ensure are set and up to date with the latest.
Need to make sure that tuned role is called during upgrade plays.
Hi, Possible fix and pr on openshift 3.9. Since there is no direct upgrade 3.10 this should fix the upgrade process. https://github.com/openshift/openshift-ansible/pull/10266 Franck
In openshift-ansible-3.9.48-1 and later, ON_QA
Try to reproduce it on openshift-ansible-3.9.43-1.git.0.d0bc600.el7.noarch openshift-ansible-3.7.71-1.git.0.30869d0.el7.noarch ============================================================================= scenario 1: v3.6-v3.7-v3.9 upgrade vs fresh install of v3.7/v3.9 ----> v3.6 [root@ip-172-18-10-199 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7.noarch tuned-profiles-atomic-openshift-node-3.6.173.0.136-1.git.0.db4569c.el7.x86_64 [root@ip-172-18-10-199 ~]# tuned-adm active Current active profile: atomic-openshift-node-guest ----> v3.6-v3.7 upgrade [root@ip-172-18-10-199 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7.noarch tuned-profiles-atomic-openshift-node-3.7.71-1.git.0.9dfa536.el7.x86_64 [root@ip-172-18-10-199 ~]# tuned-adm active Current active profile: atomic-openshift-node-guest ----> fresh v3.7 [root@ip-172-18-15-48 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7.noarch tuned-profiles-atomic-openshift-node-3.7.71-1.git.0.9dfa536.el7.x86_64 [root@ip-172-18-15-48 ~]# tuned-adm active Current active profile: openshift-control-plane ----> v3.6-v3.7-v3.9 upgrade [root@ip-172-18-10-199 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7.noarch [root@ip-172-18-10-199 ~]# tuned-adm active Current active profile: virtual-guest ----> fresh v3.9 [root@ip-172-18-0-115 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7.noarch [root@ip-172-18-0-115 ~]# tuned-adm active Current active profile: openshift-control-plane Result 1: An upgraded v3.7 does not work the same with fresh installed v3.7. An upgraded v3.9 from v3.6 does not work the same with fresh installed v3.9. =============================================================================== scenario 2: v3.7-v3.9 upgrade vs fresh install of v3.9 ----> fresh install v3.7 [root@ip-172-18-14-212 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7.noarch tuned-profiles-atomic-openshift-node-3.7.71-1.git.0.9dfa536.el7.x86_64 [root@ip-172-18-14-212 ~]# tuned-adm active Current active profile: openshift-control-plane ----> v3.7-v3.9 upgrade [root@ip-172-18-14-212 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7.noarch [root@ip-172-18-14-212 ~]# tuned-adm active Current active profile: openshift-control-plane ----> fresh install v3.9 [root@ip-172-18-0-115 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7.noarch [root@ip-172-18-0-115 ~]# tuned-adm active Current active profile: openshift-control-plane Result 2: An upgraded v3.9 works the same with fresh installed v3.9. Both of them have not rpm tuned-profiles installed and openshift-control-plane profile active. ============================================================================== Combined result 1 and result 2, this issue included two issues: 1) "openshift-control-plane" profile missed. This is because "An upgraded v3.7 does not work the same with fresh installed v3.7", which miss "openshift-control-plane" during upgrade and result that later upgrade to v3.9 miss "openshift-control-plane". This issue should be fixed in v3.7 openshift-ansible. And should be the major issue in the bug, so change target release version to v3.7.z and assign back. 2) the removed rpm tuned profile pkg. I've no idea the reason why it was removed from v3.9 installer. But according to result 2, the upgrade bahaviro is consistent with fresh install. so if this rpm tuned-profile pkg needed in v3.9, please file a new bug for both of install and upgrade of v3.9 to add rpm tuned pkg back.
We should fix and backport.
PR should address 3.9 upgrades, https://github.com/openshift/openshift-ansible/pull/10266 tuned-profile pkg not needed in v3.9+
For this bug(targeted for 3.9.z), so we focus on scenario 2: v3.7-v3.9 upgrade vs fresh install of v3.9. Other scenarios will be tracked in cloned bug. Version: openshift-ansible-3.9.77-1.git.0.b71d05a.el7.noarch.rpm ----> fresh install v3.7 [root@ip-172-18-9-33 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7_6.3.noarch tuned-profiles-atomic-openshift-node-3.7.111-1.git.0.63595b8.el7.x86_64 [root@ip-172-18-9-33 ~]# tuned-adm active Current active profile: openshift-control-plane ----> v3.7-v3.9 upgrade [root@ip-172-18-9-33 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7_6.3.noarch [root@ip-172-18-9-33 ~]# tuned-adm active Current active profile: openshift-control-plane ----> fresh install v3.9 [root@ip-172-18-13-27 ~]# rpm -qa|grep tuned tuned-2.10.0-6.el7_6.3.noarch [root@ip-172-18-13-27 ~]# tuned-adm active Current active profile: openshift-control-plane During upgrade, the tuned role was run.
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/RHBA-2019:1642