+++ This bug was initially created as a clone of Bug #1895894 +++ Description =========== When using RHSM Service (deployment/rhsm/rhsm-baremetal-ansible.yaml) based registration of the overcloud nodes and enabling the KSM the overcloud deployment will fail with following error message: "No package qemu-kvm-common available." The reason is that when the NovaComputeEnableKsm is set to true, the plan will first try to install the qemu-kvm-common before registering the nodes with Satellite. I tried to change the order of the environment import in the answers-file however it does not seem to have an effect. Steps to reproduce ================== 1. Enable RHSM: /usr/share/openstack-tripleo-heat-templates/environments/rhsm.yaml 2. Disable KSM by setting NovaComputeEnableKsm: true 3. Deploy overcloud Expected result =============== Successful deployment of the overcloud with KSM disabled on the compute nodes Actual result ============= Overcoud deployment fails with the error message: "No package qemu-kvm-common available." Environment =========== This is with OSP 16.1 --- Additional comment from Alex Schultz on 2020-11-09 17:40:56 UTC --- The ksm management in the nova-compute-container-puppet.yaml service is in host_prep_tasks. The RHSM registration is also in host_prep_tasks and you cannot specify the order. A question for the Compute folks would be can we do KSM enablement in deploy step tasks step==1 instead? --- Additional comment from Martin Schuppert on 2020-11-13 09:00:29 UTC --- Just a general node, 'NovaComputeEnableKsm: true' enables ksm, From the description it seems that you want to disable ksm, which is the default and you don't have to set anything. Yes I don't see an issue atm to move the KSM enablement in deploy step tasks step==1. --- Additional comment from Uemit Seren on 2020-11-13 09:04:34 UTC --- Yes sorry, I meant that we want to enable KSM for one role and leave it disabled for other roles (I updated the initial bug desription).
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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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/RHEA-2021:3483