Bug 2009033 - Additional Kernel Arg rcupdate.rcu_normal_after_boot=0 is not added to spoke cluster when installed via ZTP workflow
Summary: Additional Kernel Arg rcupdate.rcu_normal_after_boot=0 is not added to spoke ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Telco Edge
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.8.0
Assignee: Ian Miller
QA Contact: yliu1
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-29 18:06 UTC by yliu1
Modified: 2022-01-11 22:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-11 22:31:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2022:0021 0 None None None 2022-01-11 22:31:35 UTC

Description yliu1 2021-09-29 18:06:50 UTC
Description of problem:
Additional kernel arg included in ztp deploy image is not added to spoke cluster performance profile.


Version-Release number of selected component (if applicable):
4.8.13

How reproducible:
100%

Steps to Reproduce:
1. deploy 4.8 cluster using ztp workflow from cnf-features-deploy release-4.8 branch.
2. check kernel args

Actual results:
rcupdate.rcu_normal_after_boot=0 is not included in kernel args or performance profile on sno cluster


Expected results:
rcupdate.rcu_normal_after_boot=0 is added successfully

Additional info:
This issue does not happen when installing 4.9 from master branch of cnf-features-deploy.

Comment 1 yliu1 2021-09-29 18:19:36 UTC
Note that Marius found the ztp policy generator image has the additional kernel arg included but the generated policy does not have it.

[kni@ran-vcl01-installer cnf_tests]$ podman run -it registry.ran-vcl01.ptp.lab.eng.bos.redhat.com:5000/ztp/ztp-site-generator:4.8 cat /usr/src/hook/ztp/source-crs/PerformanceProfile.yaml
apiVersion: performance.openshift.io/v1
kind: PerformanceProfile
metadata:
  name: $name
spec:
  additionalKernelArgs:
  - "idle=poll"
  - "rcupdate.rcu_normal_after_boot=0"
  cpu:
    isolated: $isolated
    reserved: $reserved
...

[kni@ran-vcl01-installer cnf_tests]$ oc get policies -n master-1 master-1-policies.master-1-perfprofile-policy -o yaml | grep -i " additionalKern" -A 3
              additionalKernelArgs:
              - idle=poll
              cpu:
                isolated: 2-39,42-79

Comment 2 melserng 2021-09-29 20:25:59 UTC
Can we check the parent policy as we ?

Comment 3 yliu1 2021-09-29 21:27:17 UTC
How do we do that? Following is from the hub cluster if that's what you mean?

[kni@ran-vcl01-installer cnf_tests]$ oc get policies -n master-1 master-1-policies.master-1-perfprofile-policy -o yaml | grep -i " additionalKern" -A 3
              additionalKernelArgs:
              - idle=poll
              cpu:
                isolated: 2-39,42-79

Comment 6 Nick Stielau 2021-10-07 17:18:03 UTC
Assuming not a blocker for 4.9.  Please look for blocker? BZs and make a blocker determination.

Comment 12 yliu1 2021-10-12 15:48:17 UTC
This is verified on ocp 4.8.13 with latest ztp container image (4.8.0-7).

Comment 15 errata-xmlrpc 2022-01-11 22:31:15 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 (OpenShift Container Platform 4.8.26 bug fix update), 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-2022:0021


Note You need to log in before you can comment on or make changes to this bug.