Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1895894

Summary: [OSP16.1] NovaComputeEnableKsm=true and RHSM based registration not working
Product: Red Hat OpenStack Reporter: Uemit Seren <uemit.seren>
Component: openstack-tripleo-heat-templatesAssignee: Martin Schuppert <mschuppe>
Status: CLOSED ERRATA QA Contact: David Rosenfeld <drosenfe>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: aschultz, igallagh, mburns, mschuppe, smooney, uemit.seren
Target Milestone: z4Keywords: Patch, Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-11.3.2-1.20201114031840.el8ost Doc Type: If docs needed, set a value
Doc Text:
Before this update, if you had `NovaComputeEnableKsm` enabled and you were using Red Hat Subscription Management to register the overcloud Compute nodes, the `qemu-kvm-common` package failed to install. This was because the configuration was sometimes applied before the Compute nodes were registered to the required repositories. With this update, `NovaComputeEnableKsm` is enabled only after the Compute nodes are registered to the required repositories by using Red Hat Subscription Management, which ensures that the `qemu-kvm-common` package is successfully installed.
Story Points: ---
Clone Of:
: 1897601 (view as bug list) Environment:
Last Closed: 2021-03-17 15:35:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1897601    

Description Uemit Seren 2020-11-09 11:23:53 UTC
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

Comment 1 Alex Schultz 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?

Comment 4 Martin Schuppert 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.

Comment 5 Uemit Seren 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).

Comment 16 errata-xmlrpc 2021-03-17 15:35:39 UTC
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 16.1.4 director bug fix 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-2021:0817