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

Bug 2255588

Summary: tripleo_kernel_args is not applied when the new KernelArgs is subset of preceding one.
Product: Red Hat OpenStack Reporter: Keigo Noha <knoha>
Component: tripleo-ansibleAssignee: Roberto Alfieri <ralfieri>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: high Docs Contact:
Priority: high    
Version: 17.1 (Wallaby)CC: drosenfe, gregraka, jjoyce, jslagle, mariel, mburns, pgrist, prgutier, ralfieri, ramishra
Target Milestone: z4Keywords: Triaged
Target Release: 17.1   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: tripleo-ansible-3.3.1-17.1.20240918100824.8debef3.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-21 09:39:19 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:

Description Keigo Noha 2023-12-22 08:45:16 UTC 
Description of problem:
tripleo_kernel_args is not applied when the new KernelArgs is subset of preceding one. 

Let me assume that the following situation.

1st deployment with KernelArgs: "isolcpus=1,3,5,7,9,11,13,15"
2nd deployment with KernelArgs: "isolcpus=1,3,5,7,9"

At the 1st command, KernelArgs was successfully applied.
At the 2nd deployment, the new KernelArgs option is not reflected to /etc/default/grub. 


Version-Release number of selected component (if applicable):
OSP17.1

How reproducible:
Always.

Steps to Reproduce:
1. Deploy with KernelArgs
2. Then run small changes in KernelArgs which just reduce the core number of KernelArgs

Actual results:
The assigned KernelArgs is not applied to /etc/default/grub.

Expected results:
The modification to KernelAargs are always affected.

Additional info:
Comment 11 Roberto Alfieri 2024-03-25 15:43:39 UTC 
@knoha done!
Comment 42 errata-xmlrpc 2024-11-21 09:39:19 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 (RHOSP 17.1.4 bug fix and 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/RHBA-2024:9974
Comment 43 Red Hat Bugzilla 2025-03-22 04:25:07 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days