Bug 2039981 - ZTP for standard clusters installs stalld on master nodes
Summary: ZTP for standard clusters installs stalld on master nodes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Telco Edge
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.10.0
Assignee: Jim Ramsay
QA Contact: Joshua Clark
URL:
Whiteboard: Telco:RAN
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-12 20:43 UTC by Jim Ramsay
Modified: 2022-03-10 16:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:39:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift-kni cnf-features-deploy pull 902 0 None open Bug 2039981: ztp: Ensure standard cluster masters do not get stalld 2022-01-12 20:49:26 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:39:26 UTC

Description Jim Ramsay 2022-01-12 20:43:58 UTC
Description of problem:
Our ZTP profile misconfigures the "performance-patch" tuned object to always be associated with master nodes, even for standard clusters where it should only be associated with worker nodes.

How reproducible:
100%

Steps to Reproduce:
1. Install a standard cluster via ZTP
2. Check if stalld is running on master nodes and/or worker nodes

Actual results:
It is running on both master and worker nodes

Expected results:
It should only be running on worker nodes

Comment 2 Jim Ramsay 2022-01-12 22:07:47 UTC
Note: This can be checked by running `oc get mc` on the cluster under test.  If you see both `50-nto-master` and `50-nto-worker`, it's wrong.  You should see only `50-nto-worker`.

Comment 5 Joshua Clark 2022-02-22 23:03:05 UTC
Verified on both 3-node compact cluster and 5-node standard cluster.

[josclark@registry ~]$ oc get nodes
NAME                              STATUS   ROLES    AGE     VERSION
helix16.lab.eng.tlv2.redhat.com   Ready    worker   5h45m   v1.23.3+2e8bad7
helix17.lab.eng.tlv2.redhat.com   Ready    master   5h43m   v1.23.3+2e8bad7
helix23.lab.eng.tlv2.redhat.com   Ready    worker   5h45m   v1.23.3+2e8bad7
helix26.lab.eng.tlv2.redhat.com   Ready    master   6h3m    v1.23.3+2e8bad7
helix27.lab.eng.tlv2.redhat.com   Ready    master   6h3m    v1.23.3+2e8bad7


[josclark@registry ~]$ oc get pods -A |grep -i machine-config-daemon | awk {'print $2'}|\
while read NODE; do\
oc exec -n openshift-machine-config-operator $NODE -- hostname ;\
oc exec -n openshift-machine-config-operator $NODE -- pgrep stalld ;\
done

helix16.lab.eng.tlv2.redhat.com
60414
helix23.lab.eng.tlv2.redhat.com
61923
helix27.lab.eng.tlv2.redhat.com
command terminated with exit code 1
helix17.lab.eng.tlv2.redhat.com
command terminated with exit code 1
helix26.lab.eng.tlv2.redhat.com
command terminated with exit code 1

Comment 7 errata-xmlrpc 2022-03-10 16:39:13 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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056


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